1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Greetings Guest!!

    In order to combat SPAM on the forums, all users are required to have a minimum of 2 posts before they can submit links in any post or thread.

    Dismiss Notice
  3. Greetings Guest, Having Login Issues? Check this thread!
    Dismiss Notice
  4. Hail Guest!,
    Please take a moment to read this post reminding you all of the importance of Account Security.
    Dismiss Notice
  5. Author Wes Locher has teamed up with Stratics for a giveaway of his new book Braving Britannia. This book explores the history and impact of Ultima Online and includes interviews from current and past dev team members as well as many UO and Stratics community members. Click here for more details!
    Dismiss Notice


Discussion in 'UO Siege Perilous' started by kaper12, Nov 16, 2008.

  1. kaper12

    kaper12 Visitor
    Stratics Veteran

    Sep 1, 2008
    Likes Received:
    :loser:I am wondering if EA has even taken the time to do this? As someone posted in another thread they are still trying to find the hamsters never mind fixing the problem!!!

    Pinpointing and correcting slowdowns, therefore, can be a challenge.

    Monitoring tools can help locate and solve problems with latency. A quality-of-service (QoS) monitoring solution can provide the data needed to prove that the network is performing poorly or applications are slow. The monitoring solution can collect data 24/7 and send alarms automatically to notify administrators(hmmm I wonder of there are any left?) when something on the network is not performing as expected. The first step is to determine if the latency is coming from the network or the application.

    Network latency is the amount of time it takes for an application to make a request and the server to respond with an acknowledgement (a packet message used in the transmission control protocol to acknowledge receipt of a packet). Application latency is the amount of time needed for the application to process the request and send a response containing real data.

    Most network-monitoring products provide some sort of latency-monitoring features, typically either one or the other, not both. Ideally, these measurements can be graphed together over time, making clear whether the problem lies with the network or the application. Comparing the measurements of the two types of latency over time and seeing the differences can provide information that might have otherwise been overlooked.

    Graphing latency over time helps to identify patterns and anomalies that deserve closer attention. Latency monitoring can help correlate areas of latency with other relevant statistics, as well as the actual packets that occurred during that time. This type of high-resolution forensic analysis can help to detect latency problems at the highest level and drill down quickly for closer inspection.

    Being able to see graphs over time and correlate the latency is important, as latency patterns allow the administrator to compare the patterns to other events on the network, and determine the root cause of the problem. Latency monitors can include a feature that sets thresholds on latency, so alarms will go off when normal conditions are exceeded. The administrator can be made aware of excessive latency before applications on the network start dropping packets, allowing him to make necessary adjustments to the network proactively. This type of proactive latency monitoring allows the administrator to detect and correct problems in the network and applications before users notice a slowdown. :yell:
  2. Hera - Siege

    Hera - Siege Lore Master
    Stratics Veteran Stratics Legend

    Apr 3, 2004
    Likes Received:
    It certainly isn't the application, considering the Latency 'corrects' itself from time to time. If it was application, one would think it would be ever present. Unless during 'prime time' the servers do some backing up/maintenance, which I would highly doubt. An easy way to test this would be just to revert TC back 3 publishes or so...

    So from the oodles of feedback that has been already given on the subject, I would think that step one is complete. Now to figure out what piece of equipment is failing or causing the increased ping & packet loss... [Or which employee is DL'ing hardcore pR0n during their shift via rapidshare, thus nixing all their available bandwidth. :)]
  3. MaceAho

    MaceAho Guest

    Running good now, Just ran from cove to minoc no problems