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.

SI - Site Forums : Silicon Investor - Legacy Interface Discussion (2004-2011) -- Ignore unavailable to you. Want to Upgrade?

To: Rick Faurot who wrote (32)	1/13/2004 5:10:58 PM
From: SI Bob	Respond to of 6035

That's like totally weird, eh! I really hate Netscape 4.x. Long been a huge thorn in my paw. You can make mistakes like forgetting closing </td> tags and later browsers will do what you mean rather than what you say, but Netscape 4.x cuts you NO slack on such things. Edit: But that's why I keep it around. After any significant amount of development work on iHub, I'll use IE, Netscape 7, Netscape 4.x, Opera, and even a WebTV emulator on it to make sure it's working right for everyone.

To: Rick Faurot who wrote (32)	1/13/2004 6:39:19 PM
From: SI Bob	Read Replies (4) \| Respond to of 6035

Rick, since you're often trying to use SI while it's running through Molasses, could you try something for me the next time it happens? Something someone just PM'd me made me think about it. First, was it you who has that software that'll break out how much of a wait is happening at the server and how much of it is when the data's enroute? If so, the next time the site slows down, I'd love to know if maybe it's just one or both of the production servers. The code is identical on both production servers and the development server (not the one we're talking about in this thread). To use any one of the servers specifically on a page, just replace "www" with "si1", "si2", or "si3". If you find that si1 and si2 are both about equally slow but si3 is pretty fast, there's the answer. I'd need to throw si3 back into the production loop to carry some of the load. What made me think of this is that someone told me they thought SI was being non-responsive this morning then realized they had si1 bookmarked instead of www. Perhaps the problem is just the first production server? In fact, since it's past closing time right now, I'm going to go ahead and reboot si1. I don't think the site will miss a beat while that's happening.