Hi!
From here (Central-Europe), browsing this forum is desesperately slow! I wonder if you are conscious of it and if could improve this somehow... maybe with a forum reader's digest that underlines the most important posts...
Is it slow for you too?
Any other improvement idea?
PS: I ask it because i'd like to browse the forum even more - i think Celestia really rocks!
Thanks,
Thierry.
Forum is slow
this is my favourite Form
but sometimes it just draggs, bad (like tonight)
It makes it a chore sometimes
but its only sometimes
Ive logged on early and late, and its been slow both these times
and other times not.
not sure why
but sometimes it just draggs, bad (like tonight)
It makes it a chore sometimes
but its only sometimes
Ive logged on early and late, and its been slow both these times
and other times not.
not sure why
CPU- Intel Pentium Core 2 Quad ,2.40GHz
RAM- 2Gb 1066MHz DDR2
Motherboard- Gigabyte P35 DQ6
Video Card- Nvidia GeForce 8800 GTS + 640Mb
Hard Drives- 2 SATA Raptor 10000rpm 150GB
OS- Windows Vista Home Premium 32
RAM- 2Gb 1066MHz DDR2
Motherboard- Gigabyte P35 DQ6
Video Card- Nvidia GeForce 8800 GTS + 640Mb
Hard Drives- 2 SATA Raptor 10000rpm 150GB
OS- Windows Vista Home Premium 32
-
- Posts: 986
- Joined: 16.08.2002
- With us: 22 years 3 months
- Location: USA, East Coast
If you want to find out why the forum is running slowly for you, you can use the "traceroute" command ("tracert" under windows).
E.g. open a command (DOS) window and type
tracert 63.224.48.65
It'll list all of the network routers that are between you and ennui.statters.net and how long it takes each one to respond. If one of them's overloaded, its response times and the response times of the routers after it will be quite high. The time for a router to respond includes the time it takes for a test packet to get through all of the routers between you and the one being tested by traceroute. Sometimes it is quite obvious where the problem is.
Right now, I get less than 1/10 second response from all of the gateways until it gets to gw.shatters.net. That router is taking over a second to respond. It seems that right now the slowness is due to the usual problem: gw.shatters.net is overloaded. Apparently the other people who use shatters.net are running Kazaa again. *sigh*
E.g. open a command (DOS) window and type
tracert 63.224.48.65
It'll list all of the network routers that are between you and ennui.statters.net and how long it takes each one to respond. If one of them's overloaded, its response times and the response times of the routers after it will be quite high. The time for a router to respond includes the time it takes for a test packet to get through all of the routers between you and the one being tested by traceroute. Sometimes it is quite obvious where the problem is.
Right now, I get less than 1/10 second response from all of the gateways until it gets to gw.shatters.net. That router is taking over a second to respond. It seems that right now the slowness is due to the usual problem: gw.shatters.net is overloaded. Apparently the other people who use shatters.net are running Kazaa again. *sigh*
Selden
-
Topic authorThierry
i have to admit it's getting better
Thanks for your answers and the useful tracert command. This week-end the speed is ok again. I hope it will last! (if doesn't i will check my tracert result again)
My "tracert" results:
1. to 8. = about 30 ms each and then:
9. 38 ms 41 ms 41 ms bcr1-so-0-2-0.Frankfurt.cw.net [166.63.195.185]
10. 133 ms 131 ms 141 ms dcr2-loopback.NewYork.cw.net [206.24.194.100]
11. 134 ms 131 ms 131 ms agr3-so-0-0-0.NewYork.cw.net [206.24.207.58]
12. 192 ms 193 ms 190 ms acr1-loopback.Seattle.cw.net [208.172.82.61]
13. 192 ms 189 ms 193 ms bpr1-as0-0.SeattleSwitchDesign.cw.net [208.172.83.185]
14. 186 ms 193 ms 190 ms touch-america.SeattleSwitchDesign.cw.net [208.173.49.2]
15. 194 ms 189 ms 192 ms bvu-core-02.tamerica.net [205.171.5.134]
16. 192 ms 191 ms 192 ms 10.gig0-0-0.sttl-agw1.sttl.uswest.net [206.81.192.248]
17. 192 ms 194 ms 188 ms sttl-dsl-gw11.sttl.uswest.net [216.160.70.11]
18. 210 ms 209 ms 207 ms 63.224.48.70
19. 210 ms 211 ms 205 ms 63.224.48.65
That's it. First fast and then slow.
My "tracert" results:
1. to 8. = about 30 ms each and then:
9. 38 ms 41 ms 41 ms bcr1-so-0-2-0.Frankfurt.cw.net [166.63.195.185]
10. 133 ms 131 ms 141 ms dcr2-loopback.NewYork.cw.net [206.24.194.100]
11. 134 ms 131 ms 131 ms agr3-so-0-0-0.NewYork.cw.net [206.24.207.58]
12. 192 ms 193 ms 190 ms acr1-loopback.Seattle.cw.net [208.172.82.61]
13. 192 ms 189 ms 193 ms bpr1-as0-0.SeattleSwitchDesign.cw.net [208.172.83.185]
14. 186 ms 193 ms 190 ms touch-america.SeattleSwitchDesign.cw.net [208.173.49.2]
15. 194 ms 189 ms 192 ms bvu-core-02.tamerica.net [205.171.5.134]
16. 192 ms 191 ms 192 ms 10.gig0-0-0.sttl-agw1.sttl.uswest.net [206.81.192.248]
17. 192 ms 194 ms 188 ms sttl-dsl-gw11.sttl.uswest.net [216.160.70.11]
18. 210 ms 209 ms 207 ms 63.224.48.70
19. 210 ms 211 ms 205 ms 63.224.48.65
That's it. First fast and then slow.