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 : Silicon Graphics, Inc. (SGI) -- Ignore unavailable to you. Want to Upgrade?

To: Alexis Cousein who wrote (3931)	1/3/1998 12:30:00 AM
From: Patrick Gainer	Respond to of 14451

"I always expect some jobs to scale -- and people running TPC-C benchmarks always do an incredible amount of tuning, so I'd expect them to be able to get it right; as another example, I expect it to be fairly easy to e.g. use extra CPUs for geometry processing for gfx" But Alexis (and I apologize for mis-spelling your name in my last posting) the interesting thing about TPC-C on NT is that database system used is always SQL Server which uses NT kernel threads. Therefore, if nothing else, the 8 cpu TPC-C case is stressing the NT scheduler. Which in one of your previous postings you implied was the toughest part of doing a scale-able SMP OS. Even SGI's TPC-C benchmarks never stressed the SGI scheduler to any great degree. All SGI's TPC-C benchmarks used Informix as the database system, and as we all know, Informix implements its own user-level threads, within a single Irix process. Pat Pat