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 : Intel Corporation (INTC) -- Ignore unavailable to you. Want to Upgrade?

To: Joe NYC who wrote (113110)	10/11/2000 9:04:08 AM
From: rudedog	Read Replies (1) \| Respond to of 186894

Jozef - in my experience with partitioned clustered databases, which is fairly extensive, the performance of a query which executes on a single node (which would be the case for most non-optimized queries) is always at least as good as the same query executed on a single-node system of the same size when the partitioning is built into the database. The overhead to distribute the query and correlate the results is very small in comparison to the basic overhead to launch the query. I believe you are thinking about older database designs on databases which are not cluster aware - a fair amount of work was done on multiple instances of single-node database engines, using distributed 2-phase commit queries, and those do have a big performance hit if the data is local. But those designs are not needed if the base engine does the partitioning.