Big SAP-SD 2-Tier results on one 2RU server, No problem!
Tuesday Dec 06, 2005
Yeah, yeah, yeah. Ok so today there have been lots of entries on this blog about web-tier and application tier, but that is for small systems. What about a big corporate-critical kind of application, something like ERP. Won't the tiny Sun Fire T2000 (2RU - rack units)simply choke on a real beefy application like SAP?
Especially if you have database and application on the same server? Nope. (ok, ok, too many
self-written leading questions today 
, but it is kinda fun with this astoundingly cool new system)
Again the UltraSPARC T1-based server provides some really stunning performance results. The Sun Fire T2000 UltraSPARC T1 achieved great SAP-SD 2-Tier ECC 5.0 results. by supporting 950 SD Benchmark Users, 4,780 SAPS, using Open Source MaxDB Database (MySQL Distributes MaxDB). While SAP allows comparisons between different versions of the benchmark, we've found that the SAP ECC 5.0 benchmark is a heavier workload than version 4.7. But given that, let's see how it compares:
The Sun Fire T2000 beats a 4-way Xeon-based HP ProLiant DL580, ver 4.7. The Sun Fire T2000 is 8% faster than 4-way Itanium2-based HP rx4640, ver 4.7. The Sun Fire T2000 result is nearly equivalent in performance to the 4-way IBM p5 550 equipped with 1.9 GHz POWER5+
The Sun Fire T2000 result also demonstrates vertical consolidation. Both the SAP application and the open-source MaxDB database ran on the same system.
SAP doesn't like any vendor doing $/Perf, SWaP, or other kinds of derived server comparisons with their benchmark, fair enough, so those exercises are left to the reader.
...as an old boss of mine used to love to say the day after a big announcement, "what
have you done for me today ". OK, just so you know, tomorrow I foresee anouncing another new world record...
Required Footnote:
Two-tier SAP SD Standard Application Benchmark, the Sun Fire T2000 (1 processor, 8 cores, 32 threads), 1.2 GHz UltraSPARC T1 with 32 GB main memory, 1.2 GHz, 64 KB(D) + 128 KB(I) L1 cache and 3 MB L2 cache, running mySAP ERP 2004, SAP ECC Release 5.0, the MaxDB 7.5 database, Solaris 10, achieved 950 SAP SD Benchmark users, 1.91 ave dialog response time, 95,670 fully processed order line items per hour, 287,000 dialog steps per hour, 4,780 SAPS, 0.080 seconds/0.157 seconds average database requirement time (dialog/update) and 99 percent CPU utilization of the central server, Cert#2004047, More info www.sap.com/benchmark. Two-tier SAP SD standard /3 Enteprise 4.7 Standard Sales and Distribution (SD) benchmark; HP ProLiant DL580 (4-way, 4 procs, 4 cores, 4 threads) 4x 3.3 Ghz Xeon, 32 GB mem, 937 SD benchmark users, 1.96 sec avg response time, Cert#2005012, Microsoft SQL Server 2000 database, Windows Server 2003 Enterprise Edition; HP rx4640 (4-way, 4 procs, 4 cores, 4 threads) 4x 1.5 GHz Itanium2, 32xGB mem, 880 SD benchmark users, 1.89 s avg resp time, Cert#2004030, Oracle 9i Database, HP-UX11i OS. SAP, R/3, mySAP reg TM of SAP AG in Germany and other countries. More info www.sap.com/benchmark.
Background on the open-source database MaxDB
MaxDB started its life as Adabas D which was purchased by SAP AG and renamed to SapDB and used as an alternative database for SAP's application suite. Current development has been taken over by MySQL, the same company that develops the open-source MySQL database. It is released under an open-source license.
NiagaraCMT
|
|
|
|
