The Wide Finder host is at wf2.network.com
* Sun Fire T2000
* CPUs: UltraSparcT1, 32 cores
* Disks: 73GBx2 (mirrored as system disk), 136GB x 2
* RAM: 32GB
* OS: Solaris 10 U4
* Patches: Solaris 10 Recommended patches 03/29/08 release.
If you want an account, first you will need to implement a program that produces correct results on [The Benchmark] using the 100,000-line sample. Email me at tim dot bray at sun dot com, explaining your Wide Finder interest, and I'll send a pointer to the sample data.
The pkg-get command can be used to install blastwave software, see [http://www.blastwave.org/packages.php], but you have to be root. I've also made {{/usr/local}} world-writeable, so anyone with an account should be able to compile & install pretty well anything from source code. See the following links for usage notes on installed software:
* [GCC]
* [Boost]
* ...
If you get an account, you probably want to look at {{~twbray/.bash_profile}} to figure out the archaic Solaris {{$PATH}} voodoo. It's a pity Indiana isn't running on SPARC yet, it's got that friendly familiar GNU flavor.
Interesting filesystems:
* /export/home - home directories, 27G
* /wf1 - ZFS pool, 286G
* /wf1/data - ZFS filesystem, all options defaulted.
* /wf1/data/logs - logfile test data
* * O.all - Apache httpd log data, 45,275,432,643 bytes in 218,201,129 lines
* * O.1k - 1,000-line sample of O.all
* * O.10K - 10,000-line sample of O.all
* * O.100K - 100,000-line sample of O.all
* * O.1m - 1,000,000-line sample of O.all
* /wf1/data/compressed - individual compressed logfiles used to create O.all
To get a feel for the underlying I/O performance, here are the results of a 100G [Bonnie|http://www.tbray.org/ongoing/misc/Software#p-1] run:
{noformat}
-------Sequential Output-------- ---Sequential Input-- --Random--
-Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks---
Machine GB M/sec %CPU M/sec %CPU M/sec %CPU M/sec %CPU M/sec %CPU /sec %CPU
T2K 100 20.5 100 150.1 100 61.4 64.8 19.8 98.9 148.9 76.7 214 10.7
{noformat}
That CPU percentage is percent of _one core_. The results show that while the I/O performance is pretty respectable (about 150M/sec in and out), you can _easily_ saturate one of those wimpy little cores; for example, I'm pretty sure the ~20M/sec sequential-I/O numbers are CPU-limited.
* Sun Fire T2000
* CPUs: UltraSparcT1, 32 cores
* Disks: 73GBx2 (mirrored as system disk), 136GB x 2
* RAM: 32GB
* OS: Solaris 10 U4
* Patches: Solaris 10 Recommended patches 03/29/08 release.
If you want an account, first you will need to implement a program that produces correct results on [The Benchmark] using the 100,000-line sample. Email me at tim dot bray at sun dot com, explaining your Wide Finder interest, and I'll send a pointer to the sample data.
The pkg-get command can be used to install blastwave software, see [http://www.blastwave.org/packages.php], but you have to be root. I've also made {{/usr/local}} world-writeable, so anyone with an account should be able to compile & install pretty well anything from source code. See the following links for usage notes on installed software:
* [GCC]
* [Boost]
* ...
If you get an account, you probably want to look at {{~twbray/.bash_profile}} to figure out the archaic Solaris {{$PATH}} voodoo. It's a pity Indiana isn't running on SPARC yet, it's got that friendly familiar GNU flavor.
Interesting filesystems:
* /export/home - home directories, 27G
* /wf1 - ZFS pool, 286G
* /wf1/data - ZFS filesystem, all options defaulted.
* /wf1/data/logs - logfile test data
* * O.all - Apache httpd log data, 45,275,432,643 bytes in 218,201,129 lines
* * O.1k - 1,000-line sample of O.all
* * O.10K - 10,000-line sample of O.all
* * O.100K - 100,000-line sample of O.all
* * O.1m - 1,000,000-line sample of O.all
* /wf1/data/compressed - individual compressed logfiles used to create O.all
To get a feel for the underlying I/O performance, here are the results of a 100G [Bonnie|http://www.tbray.org/ongoing/misc/Software#p-1] run:
{noformat}
-------Sequential Output-------- ---Sequential Input-- --Random--
-Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks---
Machine GB M/sec %CPU M/sec %CPU M/sec %CPU M/sec %CPU M/sec %CPU /sec %CPU
T2K 100 20.5 100 150.1 100 61.4 64.8 19.8 98.9 148.9 76.7 214 10.7
{noformat}
That CPU percentage is percent of _one core_. The results show that while the I/O performance is pretty respectable (about 150M/sec in and out), you can _easily_ saturate one of those wimpy little cores; for example, I'm pretty sure the ~20M/sec sequential-I/O numbers are CPU-limited.