SI
SI
discoversearch

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 : AUTOHOME, Inc -- Ignore unavailable to you. Want to Upgrade?


To: Bnad who wrote (685)11/20/1997 11:58:00 PM
From: ftth  Respond to of 29970
 
Brad: I've been curious about the cache hit/miss data also, as well as the overall cache architecture (havn't found any info), but I don't necessarily agree that the cache is "crucial to providing high bandwidth P2P under the cable modem network's strategy." The attachment to the backbone is more key to the speed. Also, depending on the architecture, if a read miss occurs, it may be such an insignificant amount of time relative to the next available time slot in the multiplex stream that it is imperceptible except under extremely heavy loading (but I have no facts to back up this theory). Also, the downstream data path is really point-to-multipoint (or one-to-many), so a capacity limit can be reached--in theory. I've seen several articles about the studies done regarding a slowdown due to capacity overload, and they all claim (because they have a vested interest in claiming so, and no one can prove them wrong) that it's not a problem providing this condition and that condition aren't violated. For the most part I consider the test conditions unrealistically simplistic (short bursts of light bandwidth,spaced at roughly 60 second intervals, times some number of active peak-demand users) and the claims sort of misleading because they only give data for 500 or fewer drops per node, which is the absolute minimum in the system models I've seen. I can't really refute their peak usage models because they are based on projections, but most use roughly 30% peak subscriber load, which seems a bit light to me if this type of service takes off the way we're all hoping, and content bandwidth increases the way everyone is projecting.

dh



To: Bnad who wrote (685)11/21/1997 2:36:00 AM
From: Altec  Read Replies (2) | Respond to of 29970
 
> I've also read (in Rolling Stone) about a guy's
> experience with Road Runner cable modem service from Time Warner
> (he lives in a test area). The service "slows to a crawl" between
> 7 and 11 PM. And this is only under market testing conditions.

I wouldnt draw any link whatsoever between RoadRunner experiences and @Home. I have @Home; it rocks. I know people that have RR; it sucks.

The big difference is that @Home has taken a fundamentally different technical approach than anyone else out there. @Home developed their own high speed national backbone, and uses caching, replication, and other stuff to make it consistently fast. Check out their website for more info: www.home.net

RoadRUnner tried to be cheap and not do any of that. THey basically try to just plug a cable modem into the same old overloaded Internet. Simply put, it doesn't work. (I also suspect the DSL hypesters will turn some shade of green when they figure it out, too).

If you check out the Internet newsgroups, you'll see that RoadRunner customers are consistently unhappy (poor service, indifferent attitude, poor performance), and most @Home customers consistently love it. I've even heard of a group of RR customers in San Diego lobbying Time-Warner to switch to @Home!

Big difference.