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.

Non-Tech : Datek Brokerage $9.95 a trade -- Ignore unavailable to you. Want to Upgrade?

To: David Winkler who wrote (8430)	5/4/1998 1:57:00 PM
From: Rubber Man	Read Replies (1) \| Respond to of 16892

Well, when ISLD (IMO) experiences serious stress or overload, first thing to go is the real-time ISLD book (www.isld.com). From my experiences viewing updates of the book, on a stock like ENMD, it was some 15-30 second slower. That's stage one ;) Stage two is when someone accessing the ISLD book experiences re-requests (ie no data returning from ISLD). At this point the book is pretty much useless. That I've experienced previously and thought nothing of it. Recently, I've seen some really strange behavior- namely the book boots back to the open (time-travels) and goes through all the transactions since. It's acting not unlike viewing a tape, but only for ISLD transactions. When it's really messed up (like KTEL a while back) it repeats this behavior times and goes back to the open over and over again, with the replay going at several times regular speed (real-time). This I take as a hint of either ISLD blowup or bad programming, I'm betting on the former (Josh is a very talented programmer). In fact, there were a 30 second period where I received a DNS error. So, draw your own conclusions..