RE: Oracle Performance on Sunfire T2000
Date: Fri, 13 Feb 2009 01:29:54 -0700
There's one more catch with slow single thread execution with high parallelism in Oracle. If you migrate from 4 fast CPUs to 128 slow threads, you will have much heavier latch contention on busy latches. Doing whatever work under protection of a latch will probably take longer, thus the latch is held for longer. And instead of 3-4 concurrent threads trying to get the latch at the same time you'll potentially have few hundred ones....
Glenn Fawcett has quite a few useful blog entries about Oracle performance on Sun CMT processors http://blogs.sun.com/glennf/tags/throughput
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]
On Behalf Of Matthew Zito
Sent: 12 February 2009 19:02
To: jifjif_at_gmail.com; oracle-l_at_freelists.org Subject: RE: Oracle Performance on Sunfire T2000
We have a couple of t1000s, and while our workload is a little odd (we're an automation company, so all our several hundred databases do is get installed, patched, upgraded, uninstalled, etc.), anything involving data dictionary activities (running catupgd.sql, etc. - high-cpu single threaded activities) is slower on the t1000s than our ancient v210s.
Supposedly the t1000/2000 are perfect for J2EE apps - lots of threads, not a lot of heavy-lifting, parallelization of execution is the most critical piece.
http://www.freelists.org/webpage/oracle-l Received on Fri Feb 13 2009 - 02:29:54 CST