SI is slow... Speed Performance Testing

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes
SI is slow... Speed Performance Testing

An SI Board Since June 2000

Posts	SubjectMarks	Bans
17	3	0

Emcee: Green Receipt	Type: Moderated

Introduction Compact

Lately I've noticed SI has slowed down significantly. I'm not sure if the problem is on my end or if its a problem on their end.

I would like people from time to time, maybe once a week or maybe even once a day (but no more than 3 times a day) to perform the following tests and then report them on this thread. And once you start posting, please keep posting so we can build a pile of evidence...

Hopefully this information can be used as evidence as how SI can solve the problem and make everyone's experience a little more grand.

If you have access to a DOS prompt while you are connected to the internet try the following commands:

ping -a -r 9 www.siliconinvestor.com > route80.txt
notepad route80.txt

----

You will see something like this (It shouldn't be identical unless you're using the same ISP/location, etc).

Pinging v10.go2net.com [206.253.217.10] with 32 bytes of data:

Reply from 206.253.217.10: bytes=32 time=220ms TTL=247

Route: washington.dc.southeast.us.psi.net [38.1.45.201] ->

rc11.se.us.psi.net [38.1.25.203] ->

se2.isc.us.psi.net [38.1.10.5] ->

204.6.118.189 ->

sl-bb3-rly-4-0-0.sprintlink.net [144.232.7.222] ->

144.232.15.114 ->

sl-bb13-pen-10-0.sprintlink.net [144.232.5.158] ->

sl-bb11-pen-7-1.sprintlink.net [144.232.9.142] ->

sl-bb10-sea-5-2.sprintlink.net [144.232.6.117]

Request timed out.

Reply from 206.253.217.10: bytes=32 time=501ms TTL=247

Route: washington.dc.southeast.us.psi.net [38.1.45.201] ->

rc11.se.us.psi.net [38.1.25.203] ->

se2.isc.us.psi.net [38.1.10.5] ->

204.6.118.189 ->

sl-bb3-rly-0-0-0.sprintlink.net [144.232.7.218] ->

sl-bb12-rly-9-0.sprintlink.net [144.232.7.214] ->

sl-bb11-rly-7-0.sprintlink.net [144.232.9.242] ->

sl-bb13-pen-10-0.sprintlink.net [144.232.5.158] ->

sl-bb11-pen-7-1.sprintlink.net [144.232.9.142]

Reply from 206.253.217.10: bytes=32 time=170ms TTL=247

Route: washington.dc.southeast.us.psi.net [38.1.45.201] ->

rc11.se.us.psi.net [38.1.25.203] ->

se2.isc.us.psi.net [38.1.10.5] ->

204.6.118.189 ->

sl-bb3-rly-4-0-0.sprintlink.net [144.232.7.222] ->

144.232.15.114 ->

sl-bb13-pen-10-0.sprintlink.net [144.232.5.158] ->

sl-bb11-pen-7-1.sprintlink.net [144.232.9.142] ->

sl-bb10-sea-5-2.sprintlink.net [144.232.6.117]

Just paste it into a post where the evidence can be examined at a later date.

------

For control purposes, add the following to a daily post

ping 127.0.0.1 > route127.txt
notepad route127.txt

-----
it will look something like this
--

Pinging localhost [127.0.0.1] with 32 bytes of data:

Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128
Reply from 127.0.0.1: bytes=32 time<10ms TTL=128

-----

Once enough of us start posting this information SI should be able to glean what it needs to be able to fix this problem.

fwiw I'm using Windows NT...

Go to reply# or date (mm/dd/yy):

Reply	Message Preview	From	Recs	Posted
17	Me too. I haven't done a tracert to SI for about a year. As I recall previo	ILCUL8R	-	6/19/2000
16	HI, it's been awhile since i used tracert but i tried it again and its actu	Green Receipt	-	6/19/2000
15	What is the difference between PING and TRACERT? SI can always claim their slo	ILCUL8R	-	6/19/2000
14	Thanks for the post from my current location SI is rather slow and I'm get	Green Receipt	-	6/19/2000
13	Using Win2000 with a cable modem. Two slowest sites I use are WSJ and SI. WSJ	S100	-	6/19/2000
12	Pinging v10.go2net.com [206.253.217.10] with 32 bytes of data: Reply from 206	ILCUL8R	-	6/19/2000
11	You must be using Windows 98... Anyways, here is my latest ping Pinging v10.	Green Receipt	-	6/19/2000
10	Pinging v10.go2net.com [206.253.217.10] with 32 bytes of data: Reply from 206	S100	-	6/16/2000
9	that was bordering on the sluggish side....	Green Receipt	-	6/16/2000
8	Pinging v10.go2net.com [206.253.217.10] with 32 bytes of data: Request timed	S100	-	6/15/2000
7	<b>What is considered bad, good, excellent in terms of Milliseconds?</	mappingworld	-	6/15/2000
6	Time 11:30 am PDT time 15 June 2000 Pinging v10.go2net.com [206.253.217.10] wi	S100	-	6/15/2000
5	6/15/2000 9:57 ET ping -a -r 9 -w 10000 www.siliconinvestor.com > route80.tx	Green Receipt	-	6/15/2000
4	Like this? Pinging v10.go2net.com [206.253.217.10] with 32 bytes of data: Rep	WTMHouston	-	6/14/2000
3	LOL David Bowman was the human. HAL was the computer...	Green Receipt	-	6/14/2000
2	Levy was here.... first post grub. Dave o Dave o Dave are you there Da	levy	-	6/14/2000
1	on a Win98 low speed dial up line Pinging v10.go2net.com [206.253.217.10] with	Green Receipt	-	6/14/2000

Go to reply# or date (mm/dd/yy):