Sun publishes 10,000 user Siebel 8.0 PSPP benchmark on Niagara 2 systems

Here is the link to the benchmark white paper publication:

Siebel CRM Release 8.0 Industry Applications and Oracle 10gR2 DB on Sun SPARC Enterprise T5120/T5220 servers running the Solaris 10 OS

Some key highlights from the white paper:


  • All tiers of the Siebel CRM Release 8.0 architecture ran on chip multithreading (CMT) processor, UltraSPARC T2 based T5120/T5220 systems running Solaris 10 8/07.
  • Multithreading capability of the US T2 processor allowed each of the active Object Manager (OM) processes to run hundreds of Light Weight Processes (LWP), thus utilizing the available resources very effectively. A total number of 30 object managers serviced the work load of 10,000 concurrent users.
  • While supporting 10,000 concurrent Siebel users, the entire Sun Solution based on Sun SPARC Enterprise T5120/T5220 servers running Siebel CRM Release 8.0 and Oracle 10g R2 on top of Solaris 10 consumed 1202 watts in a 6U rack space. As a result the T5210/T5220 supports 8.3 users per watt of energy consumed and supports 1666 users per rack unit.
  • Apparently this is the best Siebel 8.0 benchmark result out there in terms of the number of users and price/performance. Feel free to compare Sun's 10,000 user result with other published results that you may find at Oracle Siebel Benchmark White Papers web page.

Comments:

[Trackback] Bookmarked your post over at Blog Bookmarker.com!

Posted by concurrent on January 06, 2008 at 10:37 AM PST #

Hi Giri,

Could you please provide the info on what have you done to the db server tuning to make such numbers?
I am interested in the info, how I could disable threads so that I use real cores.
I couldn't find any info on the subject so far.

Thanks

Posted by vladimir on June 20, 2008 at 02:47 AM PDT #

Vladimir,

We haven't done anything special in the database-tier to make it run better on our CMT systems. Oracle 10g RDBMS performed well out of the box. Of course we tuned the db cache and shared pool sizes accordingly to handle 10,000 concurrent Siebel users.

The SQLs in this workload (Siebel CRM, that is) are moderately complex; and are well suited to the CMT hardware. Siebel is a multi-threaded application -- so it is no surprise to see better performance on T5220s {even when compared to some of the conventional systems with very high clock speeds}.

>> [...] how I could disable threads so that I use real cores

One way is to bring some of the virtual processors off-line. You can use "psradm" as root user to turn off the processors. For example, "psradm -f 1 2 3 4 5 6 7" disables all but the very first thread within the first core of the UltraSPARC-T2 processor. "psradm -n 1 2 3 4 5 6 7" bring them back on-line. Note that the virtual processors 0-7 belong to the 1st core, 8-15 belong to core #2, 16-23 belong to core #3 etc., US-T2 processor can have up to 8 cores (0-63 virtual processors).

Before I conclude, be aware that you might not be realizing significant gains just by disabling the hardware threads ("strand" is the technical term for the hardware thread) within a core. In some cases, it may hurt the overall throughput.

Posted by Giri Mandalika on June 20, 2008 at 06:29 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Benchmark announcements, HOW-TOs, Tips and Troubleshooting

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today