By sriram on Oct 09, 2007
Today (9th Oct'07) morning - we got a Niagara 2 based server to our lab and with the help of our lab guys, we booted up this ultra cool Ultra SPARC T2 processor based Sun SPARC Enterprise T5220 server. Bringing up the server was totally a breeze - very much like Sun Fire T2000.
Like every one else, I was sure curious as to what we got here. So, once I logged in, I ran 'uname -a' and 'psrinfo' commands to find out the OS version and the processor information. Here is the sample output.- telling me that we have a 1 socket server with 64 virtual processors (translates to a 8-core with 8 thread / per core CPU) and Solaris 10 Update 4 comes pre-installed on this server.
SunOS accel 5.10 Generic_120011-12 sun4v sparc SUNW,SPARC-Enterprise-T5220
The physical processor has 64 virtual processors (0-63)
UltraSPARC-T2 (cpuid 0 clock 1417 MHz)
Being a Web Server engineer, I couldn't stop myself installing the latest Web Server 7 release - Sun Java System Web Server 7 Update 1 on this beauty and run some quick and very basic performance runs just for the heck of it.
As you might already know, Solaris 10 bundles Apache HTTPd 2 server. I decided to use this simple but efficient performance benchmarking client - 'ab' and run a very simple performance test against Web Server 7.0. So, here we go - hitting the default home page that comes with Web Server 7 (a static 'index.html')
|[root@accel]'~'> /usr/apache2/bin/ab -c 20000 -k http://accel.red.iplanet.com/index.html
This is ApacheBench, Version 2.0.41-dev <$Revision: 126.96.36.199 $> apache-2.0
Copyright (c) 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Copyright (c) 1998-2002 The Apache Software Foundation, http://www.apache.org/
Benchmarking accel.red.iplanet.com (be patient).....done
Server Software: Sun-Java-System-Web-Server/7.0
Server Hostname: accel.red.iplanet.com
Server Port: 80
Document Path: /index.html
Document Length: 12038 bytes
Concurrency Level: 20000
Time taken for tests: 0.1712 seconds
Complete requests: 1
Failed requests: 0
Write errors: 0
Keep-Alive requests: 1
Total transferred: 12297 bytes
HTML transferred: 12038 bytes
Requests per second: 584.11 [#/sec] (mean)
Time per request: 34240.000 [ms] (mean)
Time per request: 1.712 [ms] (mean, across all concurrent requests)
Transfer rate: 7009.35 [Kbytes/sec] received
Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 0 0.0 0 0
Processing: 1 1 0.0 1 1
Waiting: 1 1 0.0 1 1
Total: 1 1 0.0 1 1
Not bad huh - supporting 20,000 simultaneous connections and delivering 584 requests per second (though for a very simple static HTML page). Unfortunately, the stress client that I was using - 'ab' , had some limitations and I had to restrict myself to 20,000 simultaneous connections. Some other day, I will try this again with Faban - open source next generation benchmark runtime and see how far I can juice this workhorse for such simple static HTML pages.
Looks like, if you got Ultra SPARC T2 processor based Sun SPARC Enterprise T5220 server and a highly scalable web server on the market like Sun Java System Web Server 7, you sure could be cruising and saving a lot of money in your data center.