Silicon Investor (SI) -- The First Internet Community

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.

Technology Stocks : InfoSpace (INSP): Where GNET went! -- Ignore unavailable to you. Want to Upgrade?

To: levy who wrote (7730)	6/20/1999 10:37:00 PM
From: Jeff Dryer	Read Replies (4) \| Respond to of 28311

rlevy, My guess is that your ISP is a problem. Which Internet provider are you using? Your surfing speed/experience is dependent on a number of factors including your ISP, your connection speed, SI/Go2Net servers, Go2Net bottlenecks at our ISP InterNap, the route data packets you are requesting travel (the ability to avoid Internet traffic jams). The average time it takes for SI's servers to process a page request (and send it back over the Internet to you) is about 80ms... less than 1/10th of a second. 99.99% of all SI page requests are processed in less than a second. From home, I use MSN to connect to the Internet with a 56k modem. Just as a test, I was able to flip through the last 100 messages on the Go2Net thread in about 4 minutes 15 seconds. I went over to Yahoo and tried the same thing and it took about 5 minutes 30 seconds, but it's tough to compare because the Yahoo previous/next links keep moving up and down depending on what size ad they insert on each message page... so Yahoo is like a video game to keep the mouse on top of the next link. Each person who uses the Internet has a unique surfing experience. Even if you have a T-1 line, it can be very slow going if the Internet has lots of traffic jams. Requesting a page of information is like throwing a boomerang... your request ideally makes the round trip and comes back to you. But unfortunately, there are many routers that your request must travel through on both sides of the round trip. So, if you are living on the east coast, your request may visit a New York router, a Colorado router, a Utah router, maybe drop down and visit a California router before it makes its way to a Seattle router... these router visits are referred to as hops. You can try doing your on traceroute (which will show the hops) by going to boardwatch.internet.com I picked the MAE-EAST traceroute link and ran it for our URL techstocks.com You can do this too. Select the "trace" Query and type "techstocks.com" as the address on the following page: nitrous.digex.net Press submit and you get a trace route results page for roundtrip travel between our SI servers in Seattle and MAE-EAST (a massive router center) located in Washington D.C., which on average says that a request takes about 150 msec of travel time. Add our 80 msec processing time and you're up to 230 msec travel time on average. I've seen MAE-EAST processing times takes more than a second. MAE-WEST in California can be especially bad. Hope this helps.