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 : All About Sun Microsystems -- Ignore unavailable to you. Want to Upgrade?

To: Lizzie Tudor who wrote (54513)	6/8/2003 5:21:17 PM
From: Tom C	Respond to of 64865

The site was down, it came back up, it was slower and it was much more difficult to post. What do you think the issue is? I don't know what the issue causing slowness is but I understand that the site was shutdown and boxed up when the site was purchased by IHUB. The SUNW boxes (maybe not all of them) were shipped from Infospace to Kansas, unpacked and re-connected to the internet. The ownership of this site is merged but beside being co-located, the sites are not merged. When the site came up in Kansas things were slow. I don't believe the database conversion has happened yet. In order to do the conversion any stored procs or triggers would need to be completely rewritten. That's going to take a while given that the languages and more important the side-affects (how they behave, what they can do) are completely different. Even if no stored procedures or triggers are used and everything is straight SQL then you still need to reconcile the proprietary features that tend to be used when a system is not explicitly designed to work with multiple backends. A bigger clue that we are not yet running on a DELL/SQLServer backend or even a DELL/Oracle backend is that the site has not been shutdown so that the easy part, the data conversion can happen. So why is it slow? I don't know. It could be some things are still pointing back to Infospace servers and it's causing it to take a while. For example, some of the graphic are being served out of Seattle (InfoSpace). Maybe it's the network connectivity to Kansas or the bandwidth provided by the ISP that hosting the site? My guess is that there are still some configuration issues to work through. Maybe the web servers are dual nic'd and the static routes to the database are wrong? If I knew the answer I'd let Bob know. My opinion is that this is a locking/latching DB-OS problem just because I've seen these issues before and thats what it seems like. Msft products are weak in this area. I just posted this question to Bob. Message 19013687 Maybe that will answer things. Tom Edit ... Thing are quite fast this evening. Much faster then the last few weeks.