ScriptUO

General => Off Topic => Topic started by: Khameleon on January 29, 2009, 10:08:34 AM

Title: Client.exe CPU Hog
Post by: Khameleon on January 29, 2009, 10:08:34 AM
I just upgraded my internet becouse my POS Cousin is always running faster than me.
we run a speed test, i'm definatly faster than him in that aspect now. but his character is still skipping past me.
I have a faster computer than him we both run windows xp, he's running home, i'm running pro.
Title: Re: Client.exe CPU Hog
Post by: TrailMyx on January 29, 2009, 10:24:38 AM
Have you tried to run UOTrace on your computer and his?

UOTrace (http://support.ea.com/cgi-bin/ea.cfg/php/enduser/fattach_get.php?p_sid=dYo339pj&p_li=&p_accessibility=0&p_redirect=&p_tbl=9&p_id=536&p_created=1125176564&p_olh=0)
Title: Re: Client.exe CPU Hog
Post by: Khameleon on January 29, 2009, 10:40:17 AM
can't seem to update the server list.
Title: Re: Client.exe CPU Hog
Post by: TrailMyx on January 29, 2009, 10:52:08 AM
You can just to a trace route by hand too.  Where are you physically located in relation to your cousin?
Title: Re: Client.exe CPU Hog
Post by: Khameleon on January 29, 2009, 11:58:53 AM
about 30 miles
Title: Re: Client.exe CPU Hog
Post by: TrailMyx on January 29, 2009, 12:02:01 PM
Well you certainly have different routes to the internet then.  I'd still try a tracert on your system and his. 
Title: Re: Client.exe CPU Hog
Post by: OMGBurgers on January 29, 2009, 05:00:43 PM
download cheat engine!
hah
Title: Re: Client.exe CPU Hog
Post by: TrailMyx on January 29, 2009, 05:21:13 PM
I was refraining from saying that.  :)

Are you sure your cousin isn't already doing that?
Title: Re: Client.exe CPU Hog
Post by: Khameleon on January 30, 2009, 06:22:32 AM
ya, in 9 years he hasn't even downloaded or payed for UOA
Title: Re: Client.exe CPU Hog
Post by: 12TimesOver on January 30, 2009, 08:45:26 AM
My guess is that there is a hop between you and the server you play on with your cousin that is causing you trouble but it's a hop that your cousin doesn't have.

You don't happen to use Comcast do you?!?!

A tracert comparison will reveal many things!! :P

X
Title: Re: Client.exe CPU Hog
Post by: Cerveza on January 30, 2009, 09:33:57 AM
I like Trace3d. Nice graphic layout.
Title: Re: Client.exe CPU Hog
Post by: 12TimesOver on January 30, 2009, 11:06:16 AM
VisualRoute here!!

 :D
Title: Re: Client.exe CPU Hog
Post by: Khameleon on January 30, 2009, 11:07:16 AM
I just switched to comasts shity ass server becouse I was having this problem with at&t, now It looks like it just might be my area?
Title: Re: Client.exe CPU Hog
Post by: Khameleon on February 01, 2009, 03:35:16 PM
what Should I be pinging? each other?
Title: Re: Client.exe CPU Hog
Post by: 12TimesOver on February 02, 2009, 04:45:20 AM
Do a trace/ping to "shardname.owo.com" without the quotes.

e.g.

ping atlantic.owo.com
tracert drachenfels.owo.com

Comcast has also been known to throttle certain types of traffic, for example last year they were caught throttling BitTorrent. I'm not saying that this is the case but it wouldn't surprise me at all if there were evil intentions at play with that suck-ass ISP!!
Title: Re: Client.exe CPU Hog
Post by: Khameleon on February 02, 2009, 12:29:35 PM
My tracert

Code: [Select]
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\tracert napavalley.owo.com

Tracing route to central-aw3.owo.com [159.153.209.30]
over a maximum of 30 hops:

  1     4 ms     3 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     9 ms     9 ms     9 ms  ge-1-38-ur02.wchicago.il.chicago.comcast.net [68.86.119.77]
  4     9 ms     9 ms     9 ms  port-channel10-ur03.wchicago.il.chicago.comcast.net [68.87.231.109]
  5     9 ms     8 ms     9 ms  port-channel20-ur02.wchicago.il.chicago.comcast.net [68.87.231.105]
  6     9 ms     9 ms     9 ms  te-8-2-ur01.wchicago.il.chicago.comcast.net [68.87.230.109]
  7     9 ms    16 ms    10 ms  te-2-1-ar01.elmhurst.il.chicago.comcast.net [68.87.230.105]
  8    13 ms    11 ms    12 ms  ge-1-1-ar03.area4.il.chicago.comcast.net [68.87.230.233]
  9    35 ms    36 ms    38 ms  pos-0-13-0-0-cr01.chicago.il.ibone.comcast.net [68.86.90.53]
 10    37 ms    37 ms    43 ms  162.97.117.45
 11    41 ms    38 ms    39 ms  sl-st30-chi-.sprintlink.net [144.232.19.245]
 12    39 ms    37 ms    37 ms  sl-crs1-chi-0-3-3-0.sprintlink.net [144.232.19.181]
 13    58 ms    64 ms    58 ms  sl-crs2-che-0-0-2-0.sprintlink.net [144.232.18.120]
 14    77 ms    76 ms    77 ms  sl-crs2-stk-0-4-0-3.sprintlink.net [144.232.20.141]
 15    75 ms    76 ms    76 ms  sl-crs1-sj-0-14-0-0.sprintlink.net [144.232.24.32]
 16    76 ms    76 ms    82 ms  sl-st20-sj-0-0-0.sprintlink.net [144.232.18.106]
 17    77 ms    76 ms    76 ms  144.223.242.14
 18    78 ms    77 ms    79 ms  159.153.192.238
 19    78 ms    76 ms    77 ms  central-aw3.owo.com [159.153.209.30]

Trace complete.

Cousin's Tracert
Code: [Select]
Microsoft Windows XP [Version 5.1.2600]
 (C) Copyright 1985-2001 Microsoft Corp.
 
 C:\tracert napavalley.owo.com
 
 Tracing route to central-aw3.owo.com [159.153.209.30]
 over a maximum of 30 hops:
 
   1     *        *        *     Request timed out.
   2     8 ms     9 ms     9 ms  172.31.17.190
   3     8 ms    10 ms    11 ms  gi1-11.ccr01.ord04.atlas.cogentco.com [38.104.106.221]
   4    11 ms    10 ms    15 ms  te2-3.mpd01.ord01.atlas.cogentco.com [154.54.24.181]
   5    21 ms    22 ms    21 ms  te8-4.mpd01.mci01.atlas.cogentco.com [66.28.4.185]
   6    57 ms    67 ms    56 ms  te7-4.mpd01.sfo01.atlas.cogentco.com [154.54.6.34]
   7    56 ms    58 ms    59 ms  te7-4.mpd01.sjc01.atlas.cogentco.com [154.54.6.134]
   8    59 ms    59 ms    59 ms  te3-2.mpd01.sjc03.atlas.cogentco.com [154.54.6.82]
   9    57 ms    60 ms    60 ms  gi0-0-0.core01.sjc03.atlas.cogentco.com [154.54.6.117]
  10    58 ms    60 ms    60 ms  192.205.34.33
  11    62 ms    63 ms    63 ms  tbr1.sffca.ip.att.net [12.122.86.182]
  12    61 ms    60 ms    60 ms  gar1.sn1ca.ip.att.net [12.123.12.33]
  13    60 ms    60 ms    60 ms  12.119.139.10
  14    60 ms    61 ms    60 ms  159.153.192.238
  15    60 ms    72 ms    62 ms  central-aw3.owo.com [159.153.209.30]
 
 Trace complete.

I'm not sure what to be looking for here.
Title: Re: Client.exe CPU Hog
Post by: TrailMyx on February 02, 2009, 12:39:46 PM
My guess right there is that Sprint is BONING you...
Title: Re: Client.exe CPU Hog
Post by: Khameleon on February 02, 2009, 01:42:44 PM
can I do something about that?
what about firewall or router can I open a port?
Title: Re: Client.exe CPU Hog
Post by: TrailMyx on February 02, 2009, 02:05:09 PM
You can't do much about it since the bottleneck is quite a ways downstream from your ISP.  I guess you could bitch to your provider, but my guess is that they'll just laugh at you.  So you just have your crappy ISP to blame for it.  Any chance of switching?  You're probably DSL, so it's likely you'll have similar troubles with other ones.
Title: Re: Client.exe CPU Hog
Post by: Khameleon on February 02, 2009, 02:14:23 PM
ya I had dsl from at&t, it seemed slow, I had the mediocre speed. so I switched to comcast cable and i'm still having issues.. piss'n me off.
Title: Re: Client.exe CPU Hog
Post by: TrailMyx on February 02, 2009, 02:19:43 PM
I have a similar problem with Cox here in San Diego.  I've just learned to live with it....
Title: Re: Client.exe CPU Hog
Post by: 12TimesOver on February 03, 2009, 04:59:01 AM
Your cousin has four fewer hops than you which basically means that, right out of the gate, his packets are 20% less interfered with.

There really isn't a whole lot that you can do about it unless you started establishing your own routing tables in house and directing your traffic through different devices but this would be an extreme pain to manage at best and there is no guarantee that you wouldn't find out that the bottleneck still stands between you and a main backbone before your route changes would make a difference.

In short, I agree with TM in that there really isn't a whole lot you can do; it comes down to the traffic, quality, and routing protocols at work on the network devices used by your ISP, then their ISP, then their ISP, and they'll tell two people, and they'll tell two people, and so on, and so on.... Maybe find a different shard or let go of playing a dueling mage if you do  ;)

X
Title: Re: Client.exe CPU Hog
Post by: Khameleon on February 03, 2009, 03:34:10 PM
bummers.