Thursday May 15, 2008
Sun SPARC Enterprise M9000 server, Sybase IQ, and BMMsoft Server managed one Petabyte of raw data. That was over 6 trillion rows of transactional data and more than 185 million content-searchable documents, emails, reports, spreadsheets and other multimedia objects! This even set a new Guinness World Record™.
This is twice the size of the largest commercial data warehouse known to date.
The largest known database is Walmart which is said to have half a terabyte of data using the Teradata DB.
Thursday May 08, 2008
The Sun SPARC Enterprise M9000 configured with SPARC VI processors, Sun StorEdge 2540 Arrays, and running Solaris 10 combined with Oracle
11g achieved World Record TPC-H performance of 118,573.3 QphH@1000GB
for non-clustered systems.
The TPC-H result demonstrates that the Sun SPARC Enterprise M9000 can handle
the increasingly large databases required of DSS systems. Oracle
delivered 13 GB/sec during the benchmark. editorial note: IBM has never proven delivered IO rates? Why does IBM only resort to quoting un-obtainable peaks?
- Why no single-system 4.7GHz or 5.0GHz Power6 on TPC-H? IBM has cluster results, this allows IBM to avoid comparisons to a single system.
- The Sun SPARC Enterprise M9000 outperformed the next best competitor non-clustered system, the HP Integrity Superdome by 69%.
- The Sun SPARC Enterprise M9000 outperformed the next best competitor non-cluster system, the HP Integrity Superdome by 18% on price/performance.
- The Sun SPARC Enterprise M9000 outperformed the clustered IBM xSeries 346 by 122%.
- The Sun SPARC Enterprise M9000 outperformed the clustered IBM xSeries 346 by 29% on price/performance.
- Sun StorageTek 2540 Array disk configuration - the 20x ST2540 configuration in this benchmark delivered sustained rates of 13.7 GB/sec and showed linear scaling from 1 to 20 arrays.
- This result demonstrates the effectiveness of Solaris 10 running Oracle 11g.
TPC-H @1000GB Single-system (non-cluster) Performance Chart
QphH = the Composite Metric (bigger is better), $/QphH = the Price/Performance metric (smaller is better)
| System |
Metric QphH |
3 Year Total Sys $ |
$/QphH |
QppH |
QthH |
CPUs |
Storage Amount |
| Sun SPARC Enterprise M9000 |
118,573.3 |
$2,772,675 |
$23.38 |
114,725.4 |
122,550.2 |
32 |
34.8 TB |
| HP Superdome |
69,999.0 |
$2,008,168 |
$28.69 |
90,909.1 |
53,898.5 |
32 |
39.7 TB |
| HP Superdome |
68,100.6 |
$4,008,065 |
$59.00 |
83,041.7 |
55,847.7 |
64 |
40.6 TB |
| System |
CPU |
Cluster |
CPU MHz |
CPU |
Operating System |
Database |
RDBMS+HW Avail date |
| Sun SPARC Enterprise M9000 |
32 |
N |
2400 |
SPARC64 VI |
Solaris 10 |
Oracle 11g |
09/10/2008 |
| HP Superdome |
32 |
N |
1600 |
Itanium2 |
Windows Server 2003 |
SQL Server 2005 |
06/18/2007 |
| HP Superdome |
64 |
N |
1600 |
Itanium2 |
HP-UX 11.i V2 |
Oracle 10gR2 |
01/18/2006 |
Benchmark Description
The TPC-H benchmark is a performance benchmark established by the
Transaction Processing Council (TPC) to demonstrate Data
Warehousing/Decision Support Systems (DSS). TPC-H measurements are
produced for customers to evaluate the performance of various DSS
systems. These queries and updates are executed against a standard
database under controlled conditions. Performance projections and
comparisons between different TPC-H Database sizes (100GB, 300GB,
1000GB, 3000GB and 10000GB) are not allowed by the TPC.
TPC-H is a data warehousing-oriented, non-industry-specific benchmark
that consists of a large number of complex queries typical of decision
support applications. It also includes some insert and delete activity
that is intended to simulate loading and purging data from a warehouse.
TPC-H measures the combined performance of a particular database
manager on a specific computer system.
The main performance metric reported by TPC-H is called the TPC-H
Composite Query-per-Hour Performance Metric (QphH@SF, where SF is the
number of GB of raw data, referred to as the scale factor). QphH@SF is
intended to summarize the ability of the system to process queries in
both single and multi user modes. The benchmark requires reporting of
price/performance, which is the ratio of QphH to total HW/SW cost plus
3 years maintenance. A secondary metric is the storage efficiency,
which is the ratio of total configured disk space in GB to the scale
factor.
Disclosure Statement:
Sun SPARC Enterprise M9000 118,573.3 QphH@1000GB, $23.38/QphH@1000GB, avail 09/10/08, HP Integrity Superdome 69,999.0 QphH@1000GB, $28.69/QphH@1000GB avail 06/18/07, HP Integrity Superdome 68,100.6 QphH@1000GB, $59.00/QphH@1000GB avail 01/18/06, IBM xSeries 346 QphH@1000GB, $32.80/QphH@1000GB, avail 02/14/05,
TPC-H, QphH, $/QphH tm of Transaction Processing Performance Council
(TPC). More info www.tpc.org.
A 128-core (32-node 4-core) IBM Power 570 cluster (4.7 GHz, 64 chips, 256 threads) with DB2 is the best overall system at 10TB (343,551 QphH@10000GB, 32.89$/QphH, configuration available 04/15/08, Results as of 5/07/08).
Note: Do not divide this result by 32 to guess at single node performance, do not compare $/perf between different GB tests, these are not permitted by TPC rules!
Results Summary
- Audited Results
|
| |
- Database Size:
|
1000 GB (Scale Factor 1000) |
| |
- TPC-H Composite:
|
118,573.3 QphH@1000GB |
| |
- Price/performance:
|
$23.38/QphH@1000GB |
| |
- Available:
|
09/10/2008 for Oracle (Sun HW/SW available 05/02/2008) |
- Number of Systems:
|
One Sun SPARC Enterprise M9000 |
- Total Number Processors:
|
32 |
- Processor/MHz of Server:
|
SPARC VI 2400 MHz / 6MB L2 Cache |
- Storage:
|
34.8 Terabytes of disk |
- Database:
|
Oracle 11g |
- Operating System:
|
Solaris 10 Update 4 |
- Total 3 year Cost:
|
$2,772,675 |
- Other Performance Metrics
|
| |
- TPC-H Power:
|
114,725.4 |
| |
- TPC-H Throughput:
|
122,550.2 |
| |
- Database Load Time:
|
1:35:27 |
Wednesday Oct 31, 2007
Yesterday I posted several Sun Fire X4100 world record performance & $/performance results
on the TPC-H benchmarks. Sun leads the pack with Paraccel's innovative software and
even the software pricing model. I wanted to try to give even more insights.
ParAccel has a very efficient data compression techniques so using the
storage associated with Sun's hardware design, the Sun TPC-H cluster submissions did not need ANY external storage.
The data could be entirely contained on the internal drives of each
node. Once again, Sun is the ONLY vendor that has been able to do so.
Other vendors, using traditional RDBMS, are forced to submit results
with a disproportionate number of spindles, in order to achieve
competitive performance, even at small scale factors.
As a consequence, the Sun ParAccel cluster solution greatly reduces
costs and requirements for space, power/cooling, maintenance and
complex hardware administration.
Sun and ParAccel are in the remarkably unique position of
having simultaneously the best performance and price/performance
by far at multiple TPC-H scale factors. As I said yesterday, innovators
seek out and find innovators.
The ParAccel Analytic Database is an innovative RDBMS designed
from the ground up as Decision Support and Business Intelligence
database.
ParAccel has a parallel cluster architecture, "shared-nothing",
with node redundancy, which relies on a column-based table
structure and heavy data compression. Compression provides for
a significantly smaller data footprint, higher speed in data
processing and transmission. The significant reduction in the
size of the data allows for even large databases to be fully
contained in the memory of a cluster of multiple systems.
The database can also operate by accessing data on permanent
storage, although with a tradeoff in performance.
ParAccel doesn't make use of complex index structures, further
reducing database size, administration complexity and simplifying
data updates.
Data partitioning and load balancing is provided automatically
by the ParAccel product and doesn't require manual DB admin
intervention, either to optimize the data layout or to create
additional indexes and structures, traditionally needed
to speedup query performance.
Results detailed at:
http://blogs.sun.com/bmseer/entry/innovation_setting_world_records_in
http://blogs.sun.com/bmseer/entry/tpc_h_100gb_sun_fire
http://blogs.sun.com/bmseer/entry/sun_paraccel_in_tpc_h
Disclosure Statement:
TPC-H @1000GB Sun Fire X4100 cluster 315,842.9 QphH@1000GB, $4.57/QphH@1000GB, avail 10/29/07; TPC-H @300GB Sun Fire X4100 cluster 198,578.1 QphH@300GB, $3.15/QphH@300GB, avail 10/29/07; TPC-H @100GB Sun Fire X4100 cluster 98,857.0 QphH@100GB, $2.65/QphH@100GB, avail 10/29/07; TPC-H, QphH, $/QphH tm of Transaction Processing Performance Council (TPC). More info http://www.tpc.org.
Tuesday Oct 30, 2007
Paraccel & Sun didn't just do one benchmark, we did it at three different
sizes: TPC-H 1000GB, TPC-H 300GB, and now the 100GB details below.
in the TPC-H 1000GB blog entry we also talked about Paraccel's pricing innovations.
This benchmark result demonstrates that a shared-nothing cluster of Sun Fire X4100s achieves the best performance and, simulatenously, the best price/performance among all TPC-H@100GB submissions. Each of the 15 node in the cluster was powered by 2 dual-core 2.8GHz Opteron processors.
Specifically, the Sun Fire X4100 cluster achieved a QphH@100GB of 98,857 together with $/QphH@100GB of $2.65. The performance is more than 5 times the previously reported best performance and the price/performance is almost twice as good as the previously reported best price/performance.
Competitive Landscape TPC-H @100GB Performance:
$/QphH = TPC-H Price/Performance metric (smaller is better)
QphH = TPC-H Composite Metric (bigger is better)
| System |
Socket/
Core/
Thread |
CPU Type GHz |
QphH |
$/
QphH
|
Total $ |
DBMS
|
Avail |
# Clust node |
Sun Fire X4100
|
30/ 60/ 60
|
Opt 2.8GHz |
98,857 |
2.65
|
263,460.06
|
Paraccel
|
10/29/07 |
15 |
HP DL585 G2
|
4/ 8/ 8
|
Opt 2.8GHz |
19323
|
10.67
|
205,988
|
SQLS
|
1/16/07 |
1 |
Dell PE6950
|
4/ 8/ 8 |
Opt 2.8GHz |
17180
|
7.64
|
131,204
|
SQLS
|
12/04/06 |
1 |
HP DL580 G4
|
4/8/8 |
Xeon 3.4GHz |
17120
|
7.91
|
135,384
|
SQLS
|
11/22/06 |
1 |
Dell PE2900
|
2/ 8/ 8 |
Xeon 2.66GHz |
15724
|
7.45
|
117,022
|
SQLS
|
12/31/06 |
1 |
IBM eSvr 325
|
16/ 16/ 16 |
Opteron 2.0GHz |
12216
|
70.68
|
863,410
|
DB2
|
11/08/03 |
8 |
TPC-H @100GB Price-Performance:
$/QphH = TPC-H $/Perf metric (smaller better)
QphH = TPC-H Composite Metric (bigger better)
| System |
Socket/
Core/
Thread |
CPU GHz |
QphH |
$/
QphH
|
Total $ |
DBMS
|
Avail |
# of
Clust
Node
|
Sun Fire X4100
|
30/ 60/ 60
|
Opt 2.8 GHz |
98,857.0
|
2.65
|
263,460.06
|
Paraccel
|
10/29/07 |
15 |
HP ML370G5
|
1/4/4
|
Xeon 2.66 GHz |
4521
|
4.30
|
19,437
|
SQLS
|
7/31/07 |
1 |
Sun Fire X4100
|
2/ 2/ 2
|
Opt 3.0GHz |
4132
|
4.61
|
19,057
|
SybIQ
|
6/23/06 |
1 |
Sun Fire X4100M2
|
2/ 4/ 4 |
Opt 3.0 GHz |
8587
|
5.29
|
45,467
|
SybIQ
|
5/25/07 |
1 |
Dell PE6950
|
4/ 8/ 8 |
Opt 2.8GHz |
14923
|
5.66
|
84,387
|
SQLS
|
12/04/06
|
1 |
Dell PE6950
|
4/ 8/ 8 |
Opt 2.8GHz |
17180
|
7.64
|
131,204
|
SQLS
|
12/04/06 |
1 |
HP DL580 G4
|
4/ 8/ 8 |
Xeon 3.4GHz |
17120
|
7.91
|
135,384
|
SQLS
|
11/22/06 |
1 |
Benchmark Description
The TPC-H benchmark
is a performance benchmark established by the Transaction Processing
Council
(TPC) to demonstrate Data Warehousing/Decision Support Systems (DSS).
TPC-H
measurements are produced for customers to evaluate the performance of
various DSS systems. These queries and updates are executed against a
standard
database under controlled conditions. Performance projections and
comparisons
between different TPC-H Database sizes (100GB, 300GB, 1000GB, 3000GB
and
10000GB) are not allowed by the TPC.
TPC-H is a
data warehousing-oriented,
non-industry-specific benchmark that consists of a large number of
complex
queries typical of decision support applications. It also includes some
insert and delete activity that is intended to simulate loading and
purging
data from a warehouse. TPC-H measures the combined performance of a
particular
database manager on a specific computer system.
The main performance
metric reported by TPC-H is called the TPC-H Composite Query-per-Hour
Performance
Metric (QphH@SF, where SF is the number of GB of raw data, referred to
as the scale factor). QphH@SF is intended to summarize the ability of
the
system to process queries in both single and multi user modes. The
benchmark
requires reporting of price/performance, which is the ratio of QphH to
total HW/SW cost plus 3 years maintenance. A secondary metric is the
storage
efficiency, which is the ratio of total configured disk space in GB to
the scale factor.
Disclosure Statement:
TPC-H @100GB
Sun Fire X4100 cluster 98,857.0 QphH@100GB, $2.65/QphH@100GB, avail 10/29/07;
TPC-H, QphH, $/QphH tm of
Transaction Processing Performance Council (TPC).
More info http://www.tpc.org.
See Also:
TPC-H Scale Factor 100 (SF100 - 100GB) benchmark.
| Audited Results |
|
Database Size: |
100 GB (Scale Factor 100) |
|
TPC-H Composite: |
98,857 QphH@100GB |
|
$/perf: |
$2.65 / QphH@100GB |
|
Available |
Oct 29, 2007 |
| # of Systems: |
15 x Sun Fire X4100
each X4100:
16GB memory each,
2 x 146GB (10k RPM) internal SAS each
|
| Total # Procs: |
30
|
| Total # Cores: |
60
|
| Total # Threads: |
60
|
| Processor/GHz of Server: |
Opteron/2.8 GHz Dual-core
|
| Storage: |
4079 Gigabytes of disk |
| Database: |
Paraccel Analystic Database |
| Operating System: |
RedHat Enterprise Linux 4.4 |
| Total 3 year Cost: |
$263,460.06 |
| Other Performance Metrics |
|
TPC-H Power: |
70,827.4
|
|
TPC-H Throughput: |
137,979.1
|
|
Database Load Time |
10 minutes 42 seconds
|
|
Storage Ratio: |
40.08
|
|
Tuesday Oct 30, 2007
This benchmark result demonstrates that a shared-nothing cluster of Sun Fire X4100s achieves the best performance and, simulatenously, the best price/performance among all TPC-H@300GB submissions. Each of the 30 node in the cluster was powered by 2 dual-core 2.8GHz Opteron processors.
Specifically, the Sun Fire X4100 cluster achieved a QphH@300GB of 198,578 together with $/QphH@300GB of $3.15. The performance is almost 5 times the previously reported best performance and the price/performance is more than twice as good as the previously reported best price/performance.
For other Other Innovations see:
http://blogs.sun.com/bmseer/entry/innovation_setting_world_records_in
TPC-H @300GB Performance:
$/QphH = TPC-H Price/Performance metric (smaller is better)
QphH = TPC-H Composite Metric (bigger is better)
| System |
Socket
/Core/
Thread |
CPU Type GHz |
QphH |
$/
QphH
|
total price |
DBMS
|
Avail |
# Clust Nodes |
Sun Fire X4100
|
60/ 120/ 120
|
Opt 2.8GHz |
198,578 |
3.15
|
624,770
|
Paraccel
|
10/29/07 |
30 |
HP BL480c
|
16/ 32/ 32
|
Opt 3.0GHz |
40411
|
18.67
|
754,232
|
Oracle
|
12/18/06 |
8 |
HP BL460c
|
16/ 32/ 32 |
Xeon 3.0GHz |
39614
|
12.57
|
497,869
|
Oracle
|
9/15/07
|
8 |
Dell PE6800
|
8/ 16/ 32 |
Xeon 3.0GHz |
18881
|
24.37
|
460,004
|
Oracle
|
4/24/06
|
2 |
IBM eSvr 325
|
16/ 16/ 16 |
Opt 2.0GHz |
13195
|
65.44
|
863,410
|
DB2
|
11/08/03
|
8 |
TPC-H @300GB Price-Performance:
$/QphH = TPC-H Price/Performance metric (smaller is better)
QphH = TPC-H Composite Metric (bigger is better)
| System |
Socket/
Core/
Thread |
CPU Type GHz |
QphH |
Price/
QphH
|
Price
in
US dollars
|
DBMS
|
Available |
#
Clust
Nodes
|
Sun Fire X4100
|
60/120/120
|
Opteron 2.8 GHz |
198578
|
3.15
|
624,770
|
Paracell
|
10/29/07 |
30 |
Sun Fire X4100M2
|
2/ 4/ 4 |
Opt 3.0 GHz |
7641
|
5.89
|
45,001
|
SybIQ
|
5/25/07
|
1 |
Sun Fire X4200
|
2/ 2/ 2
|
Opt 3.0GHz |
4936
|
6.29
|
31,033
|
SybIQ
|
6/23/06 |
1 |
HP DL585 G1
|
4/ 4 /4 |
Opt 2.4GHz |
12226
|
11.71
|
143,041
|
SQLS
|
1/26/06 |
1 |
HP BL460c
|
16/ 32/ 32 |
xeon 3.0GHz |
39614
|
12.57
|
497,869
|
Oracle
|
9/15/07 |
8 |
HP DL585 G2
|
4/ 8/ 8 |
Opt 2.8GHz |
18299
|
13.67
|
250,057
|
SQLS
|
4/19/07
|
1 |
IBM x3650
|
2/ 4/ 4 |
Xeon 3.0GHz |
10165
|
15.40
|
156,535
|
DB2
|
10/06/06
|
1 |
Dell 6800
|
8/ 8/ 8 |
Xeon 3.33GHz |
11743
|
21.84
|
256,383
|
Oracle
|
1/08/06 |
2 |
Benchmark Description
The TPC-H benchmark
is a performance benchmark established by the Transaction Processing
Council
(TPC) to demonstrate Data Warehousing/Decision Support Systems (DSS).
TPC-H
measurements are produced for customers to evaluate the performance of
various DSS systems. These queries and updates are executed against a
standard
database under controlled conditions. Performance projections and
comparisons
between different TPC-H Database sizes (100GB, 300GB, 1000GB, 3000GB
and
10000GB) are not allowed by the TPC.
TPC-H is a
data warehousing-oriented,
non-industry-specific benchmark that consists of a large number of
complex
queries typical of decision support applications. It also includes some
insert and delete activity that is intended to simulate loading and
purging
data from a warehouse. TPC-H measures the combined performance of a
particular
database manager on a specific computer system.
The main performance
metric reported by TPC-H is called the TPC-H Composite Query-per-Hour
Performance
Metric (QphH@SF, where SF is the number of GB of raw data, referred to
as the scale factor). QphH@SF is intended to summarize the ability of
the
system to process queries in both single and multi user modes. The
benchmark
requires reporting of price/performance, which is the ratio of QphH to
total HW/SW cost plus 3 years maintenance. A secondary metric is the
storage
efficiency, which is the ratio of total configured disk space in GB to
the scale factor.
Disclosure Statement:
TPC-H @300GB
Sun Fire X4100 cluster 198,578.1 QphH@300GB, $3.15/QphH@300GB, avail 10/29/07;
TPC-H, QphH, $/QphH tm of
Transaction Processing Performance Council (TPC).
More info http://www.tpc.org.
See Also:
Results Summary TPC-H SF300 - 300GB benchmark
| Audited Results |
|
Database Size: |
300 GB (Scale Factor 300) |
|
TPC-H Composite: |
198,578 QphH@300GB |
|
Price/performance: |
$3.15 / QphH@300GB |
|
Available |
Oct 29, 2007 |
| Number of Systems: |
30 x Sun Fire X4100
each X4100:
16GB memory each,
2 x 146GB (10k RPM) internal SAS each
|
| Total Number Processors: |
60
|
| Total Number Cores: |
120
|
| Total Number Threads: |
120
|
| Processor/GHz of Server: |
Opteron/2.8 GHz Dual-core
|
| Storage: |
8158 Gigabytes of disk |
| Database: |
Paraccel Analystic Database |
| Operating System: |
RedHat Enterprise Linux 4.4 |
| Total 3 year Cost: |
$624,770.12 |
| Other Performance Metrics |
|
TPC-H Power: |
145,219.3
|
|
TPC-H Throughput: |
271,542.9
|
|
Database Load Time |
15 minutes 5 seconds
|
|
Storage Ratio: |
27.19
|
|
Tuesday Oct 30, 2007
Innovation is an infectious thing in a very good way. Innovators seek
out innovators to get even greater things. This is a story that is all
about that. Customer wanted innovative hardware, they came to Sun,
customer was interested in new database software (Paraccel). We saw
each other's innovations, did some test, made some plans, and became
quick friends. Wait till we apply a few more innovative things and
make things even better.
Sun Fire X4100 using Paraccel Analytic Database sets World Record Performance and Price/Performance for the TPC-H @1000GB.
This benchmark result demonstrates that a shared-nothing cluster of Sun Fire X4100s achieves the best performance and at the same time the best price/performance amongst all TPC-H@1000GB submissions. Each of the 48 node in the cluster was powered by 2 dual-core 2.8GHz Opteron processors.
The best thing:The Paraccel Analytic Database isn't about setting benchmark world records.
It SETS world records because it is designed to do industrial strength everyday DSS. If you need this kind of database work for mission critical activities you should get to know Paraccel.
The benchmark details: the Sun Fire X4100 cluster achieved a QphH@1000GB of 315,842 together with $/QphH@1000GB of $4.57. The performance is almost 5 times the previously reported best performance and the price/performance is almost twice as good as the previously reported best price/performance.
Other Innovations:
Another key area of innovation is business model. I've long complained
about pricing a gallon of automotive gasoline by the number of cylinders
in each particular car (wow that sounds silly) - whoops, I mean pricing
software by # of cores. Paraccel Analytic Database innovates here as well.
Databases manage data, pricing is tied to the amount of data managed. Fair and
easy to measure and related to what the software does. The majors could
learn from Paraccel in this area as well.
TPC-H @SF1000GB Performance Table:
$/QphH = TPC-H Price/Performance metric (smaller is better)
QphH = TPC-H Composite Metric (bigger is better)
| System |
Socket
/Core/
Thread |
CPU Type GHz |
QphH |
$/
QphH
|
Total Price |
DBMS
|
Avail |
# Clust node |
Sun Fire X4100
|
96/ 192/ 192
|
Opt 2.8GHz
|
315,842
|
4.57
|
624,770
|
Paraccel
|
10/29/07 |
48 |
HP Super- dome
|
32/ 64/ 64 |
Itan2 1.6GHz |
69,999
|
28.69
|
2,008,168
|
SQLS
|
6/18/07 |
1 |
HP Super- dome
|
64/ 64/ 64 |
Itan2 1.6GHz |
68,101
|
59.00
|
4,008,065
|
Oracle
|
1/18/06 |
1 |
IBM eSvr 346
|
64/ 64/ 128 |
Xeon 3.6GHz |
53,451
|
32.80
|
1,753,144
|
DB2
|
2/14/05 |
64 |
HP DL585
|
48/ 48/ 48 |
Opt 2.2GHz
|
35,141
|
59.93
|
2,106,123
|
Oracle
|
10/21/04 |
12 |
Bull 6320
|
32/ 32/ 32 |
Itan2 1.6GHz |
34,988
|
38.41
|
1,343,811
|
Oracle
|
2/02/06 |
1 |
TPC-H @1000GB Price-Performance Table:
$/QphH = TPC-H Price/Performance metric (smaller is better)
QphH = TPC-H Composite Metric (bigger is better)
| System |
Socket/
Core/
Thread |
CPU Type GHz |
QphH |
$/
QphH
|
Price
in
US dollars
|
DBMS
|
Available |
#
Cluster
Node
|
Sun Fire X4100
|
96/ 192/ 192
|
Opt 2.8GHz |
315842
|
4.57
|
624,770
|
Paraccel
|
10/29/07 |
48 |
Sun Fire X4500 G2
|
2/ 4/ 4
|
Opt 2.8 GHz |
5604
|
8.11
|
45,439
|
SybIQ
|
10/15/07 |
1 |
HP DL585 G2
|
4/ 8/ 8
|
Opt 2.8GHz |
14772
|
9.73
|
143,736
|
SQLS
|
04/25/07 |
1 |
Bull 3045
|
4/ 8/ 16 |
Itan2 1.6GHz |
12087
|
12.56
|
151,870
|
SQLS
|
03/06/07
|
1 |
HP DL585 G1
|
4/ 4/ 4 |
Opt 2.4GH |
10493
|
13.85
|
145,264
|
SQLS
|
03/02/06
|
1 |
Bull 5651
|
16/ 16/ 16 |
Itan2 1.6GHz |
17059
|
25.48
|
434,553
|
SQLS
|
05/08/06
|
1 |
IBM eSvr 346
|
64/ 64/ 128 |
Xeon 3.6GHz |
53451
|
32.80
|
1,753,144
|
DB2
|
02/14/05
|
64 |
Benchmark Description
The TPC-H benchmark
is a performance benchmark established by the Transaction Processing
Council
(TPC) to demonstrate Data Warehousing/Decision Support Systems (DSS).
TPC-H
measurements are produced for customers to evaluate the performance of
various DSS systems. These queries and updates are executed against a
standard
database under controlled conditions. Performance projections and
comparisons
between different TPC-H Database sizes (100GB, 300GB, 1000GB, 3000GB
and
10000GB) are not allowed by the TPC.
TPC-H is a
data warehousing-oriented,
non-industry-specific benchmark that consists of a large number of
complex
queries typical of decision support applications. It also includes some
insert and delete activity that is intended to simulate loading and
purging
data from a warehouse. TPC-H measures the combined performance of a
particular
database manager on a specific computer system.
The main performance
metric reported by TPC-H is called the TPC-H Composite Query-per-Hour
Performance
Metric (QphH@SF, where SF is the number of GB of raw data, referred to
as the scale factor). QphH@SF is intended to summarize the ability of
the
system to process queries in both single and multi user modes. The
benchmark
requires reporting of price/performance, which is the ratio of QphH to
total HW/SW cost plus 3 years maintenance. A secondary metric is the
storage
efficiency, which is the ratio of total configured disk space in GB to
the scale factor.
Disclosure Statement:
TPC-H @1000GB
Sun Fire X4100 cluster 315,842.9 QphH@1000GB, $4.57/QphH@1000GB, avail 10/29/07;
TPC-H, QphH, $/QphH tm of
Transaction Processing Performance Council (TPC).
More info http://www.tpc.org.
See Also:
Results Summary
| Audited Results |
|
Database Size: |
1000 GB (Scale Factor 1000) |
|
TPC-H Composite: |
315,842 QphH@1000GB |
|
Price/performance: |
$4.57 / QphH@1000GB |
|
Available |
Oct 29, 2007 |
| Number of Systems: |
48 x Sun Fire X4100,
each X4100:
16GB memory each,
2 x 146GB (10k RPM) internal SAS each |
| Total # Procs: |
96
|
| Total # Cores: |
192
|
| Total # Threads: |
192
|
| Processor GHz: |
Opteron/2.8 GHz Dual-core
|
| Storage: |
13053 Total Gbytes of disk |
| Database: |
Paraccel Analytic Database |
| Operating System: |
RedHat Enterprise Linux 4.4 |
| Total 3 year Cost: |
$1,442,050.52 |
| Other Performance Metrics |
|
TPC-H Power: |
289,877.5
|
|
TPC-H Throughput: |
344,134.1
|
|
Database Load Time |
41 minutes 44 seconds
|
|
Storage Ratio: |
13.05
|
|
Wednesday Oct 17, 2007
The Sun Fire X4500 system running Solaris 10 and
Sybase IQ 12.6 achieved a new TPC-H Price/Performance World Record
of $8.11 USD $/QphH@1000GB. (Sun Fire X4500 was code-named "Thumper")
The single Sun Fire X4500 beat the previous best Price/Performance
result, the HP DL585 G2 16%, and is the only 2-socket submission at 1000GB
The total storage in this Sun configuration was 11.2TB and it still allowed it to set the price/performance record on this 1TB Benchmarks (1TB ~= SF1000 = 1000GB). Lowest total cost of ownership ($45,439) of ANY submission at
1000GB and less than 1/3rd of the cost of the HP DL585 G2 total configuration.
The TPC-H result demonstrates the Sun Fire X4500 capabilities as
a database machine. Each node of the X4500 cluster delivered 1.5
GB/sec of real IO throughput for a total of 1.5 GB/sec.
The TPC-H result demonstrates the effectiveness of Solaris 10
running Sybase IQ and results on the Opteron processors.
Another "warehouse in a box" result from Sun. To date, Sun is the only
vendor to be able to produce "in the box" TPC-H results of any kind.
TPC-H @1000GB Performance Chart (to be added, sorry it is very late right now)
QphH = the Composite Metric (bigger is better)
$/QphH = the Price/Performance metric (smaller is better)
QppH = the Power Numerical Quantity
QthH = the Throughput Numerical Quantity
| System |
Sockets/
Cores/
Threads |
CPU Type |
GHz |
QphH |
Price/
QphH
|
Price
in
currency
|
DBMS
|
Available |
Disk
Data
Ratio
|
Sun Fire X4500
|
2/4/4
|
Opteron
|
2.8
|
5604
|
8.11
|
45,439 $US
|
SybIQ
|
10/15/07 |
11.2 |
HP DL585 G2
|
4/8/8
|
Opteron
|
2.8
|
14773
|
9.73
|
143,736 $US
|
SQLS
|
04/25/07 |
7.8 |
Bull 3045
|
4/8/16 |
Itanium
|
1.6
|
12087
|
12.56
|
151,870 $US
|
SQLS
|
03/06/07
|
5.7 |
HP DL585 G1
|
4/4/4 |
Opteron
|
2.4
|
10493
|
13.85
|
145,264 $US
|
SQLS
|
03/02/06
|
6.4 |
Bull 5651
|
16/16/16 |
Itanium
|
1.6
|
17060
|
25.48
|
434,553 $US
|
SQLS
|
05/08/06
|
9.3 |
Sun Fire V490
|
4/8/8 |
US-IV+
|
1.5
|
4368
|
31.17
|
136,121 $US
|
SybIQ
|
01/05/06
|
2.7 |
Details of the Sun X4500 test
Complete benchmark results may be found at the TPC benchmark website http://www.tpc.org.
Benchmark Description
The TPC-H benchmark is a performance benchmark established by the
Transaction Processing Council (TPC) to demonstrate Data
Warehousing/Decision Support Systems (DSS). TPC-H measurements are
produced for customers to evaluate the performance of various DSS
systems. These queries and updates are executed against a standard
database under controlled conditions. Performance projections and
comparisons between different TPC-H Database sizes (100GB, 300GB,
1000GB, 3000GB and 10000GB) are not allowed by the TPC.
TPC-H is a data warehousing-oriented, non-industry-specific benchmark
that consists of a large number of complex queries typical of decision
support applications. It also includes some insert and delete activity
that is intended to simulate loading and purging data from a warehouse.
TPC-H measures the combined performance of a particular database
manager on a specific computer system.
The main performance metric reported by TPC-H is called the TPC-H
Composite Query-per-Hour Performance Metric (QphH@SF, where SF is the
number of GB of raw data, referred to as the scale factor). QphH@SF is
intended to summarize the ability of the system to process queries in
both single and multi user modes. The benchmark requires reporting of
price/performance, which is the ratio of QphH to total HW/SW cost plus
3 years maintenance. A secondary metric is the storage efficiency,
which is the ratio of total configured disk space in GB to the scale
factor.
Disclosure Statement:
Sun Fire X4500 5,604.9 QphH@1000GB, $8.11 USD $/QphH@1000GB, avail
10/15/07; HP DL585 G2, 14,773 QphH@1000GB, $9.73 USD $/QphH@1000GB, avail
4/25/07; TPC-H, QphH, $/QphH tm of Transaction Processing
Performance Council (TPC). More info www.tpc.org.
Results Summary SF1000 (SF1000 = 1000GB) benchmark
| Audited Results |
| |
Database Size: |
1000 GB (Scale Factor 1000) |
| |
TPC-H Composite: |
5,604.9 QphH@1000GB |
| |
Price/performance: |
$8.11 USD $/QphH@1000GB |
| |
Available: |
October 15, 2007 |
| Number of Systems: |
one Sun Fire X4500 |
| Total Number Processors: |
2 |
| Processor/MHz of Server: |
AMD Dual Core Opteron Model 290 2.8 GHz |
| Storage: |
11.18 Terabytes of disk |
| Database: |
Sybase IQ 12.6 |
| Operating System: |
Solaris 10 |
| Total 3 year Cost: |
$45,439.50 USD |
| Other Performance Metrics |
| |
TPC-H Power: |
6,446.1 |
| |
TPC-H Throughput: |
4,873.5 |
| |
Database Load Time: |
10 hours 5 minutes |
Wednesday Oct 17, 2007
The 10-node Sun Fire X4500 cluster running Solaris 10 and
IBM DB2 9.1 achieved a new TPC-H Price/Performance World Record
of $29.39 USD $/QphH@3000GB. (Sun Fire X4500 was code-named "Thumper")
The Sun Fire X4500 cluster beat the previous best Price/Performance
result, the IBM xSeries 346 cluster by 9%.
The total storage in this Sun configuration was 218TB and it still allowed it to set the price/performance record on this 3TB Benchmarks (3TB ~= SF3000 = 3000GB).
With this result, Sun systems running Solaris 10 now hold 2 of the top
4 price/performance results on the TPC-H@3000GB benchmark and 3 of the top 10.
The TPC-H result demonstrates the Sun Fire X4500 capabilities as
a database machine. Each node of the X4500 cluster delivered 1.5
GB/sec of real IO throughput for a total of 15 GB/sec.
The TPC-H result demonstrates the effectiveness of Solaris 10
running DB2 and results on the Opteron processors.
TPC-H @3000GB Performance Chart
QphH = the Composite Metric (bigger is better)
$/QphH = the Price/Performance metric (smaller is better)
QppH = the Power Numerical Quantity
QthH = the Throughput Numerical Quantity
| System |
Composite (QphH) |
3 Year Total System Cost |
$/perf $/QphH |
Power (QppH) |
Through- put (QthH) |
Proc |
Storage Amount |
| Sun Fire X4500 |
38,672.4 |
$1,136,536 |
$29.39 |
51,320.0 |
29,141.8 |
20 |
218.3 TB |
| IBM xSeries 346 |
54,465.9 |
$1,761,686 |
$32.34 |
90,854.7 |
32,651.4 |
64 |
25.6 TB |
| HP Superdome |
60,359.3 |
$1,967,970 |
$32.60 |
80,838.3 |
45,068.3 |
32 |
32.9 TB |
| Sun Fire E25K |
114,713.7 |
$4,207,126 |
$36.68 |
136,798.4 |
96,194.3 |
72 |
63.3 TB |
| HP Proliant BL25p |
110,576.5 |
$4,179,238 |
$37.80 |
116,379.3 |
105,063.0 |
64 |
69.6 TB |
| Unisys ES7000/one |
30,013.4 |
$1,135,354 |
$37.83 |
38,395.9 |
23,460.9 |
16 |
27.8 TB |
| HP rx8640 |
37,813.7 |
$1,433,521 |
$37.92 |
51,160.6 |
27,948.8 |
16 |
22.6 TB |
| Unisys ES7000 Orion |
26,246.1 |
$1,169,880 |
$44.58 |
33,415.8 |
20,614.7 |
32 |
23.8 TB |
| IBM p595 |
100,512.3 |
$5,358,874 |
$53.32 |
132,598.2 |
76,190.5 |
64 |
37.7 TB |
| Sun Fire E25K |
105,430.9 |
$5,784,902 |
$54.87 |
121,805.8 |
91,257.4 |
72 |
94.8 TB |
| HP Superdome |
71,847.8 |
$4,008,065 |
$55.79 |
92,335.6 |
55,905.9 |
64 |
40.6 TB |
| System |
Proc |
cluster |
CPU MHz |
Type |
Operating System |
Database |
RDBMS+HW Available |
| Sun Fire X4500 |
20 |
Y |
2600 |
AMD Opteron 285 |
Solaris 10 |
DB2 9.1 |
10/12/2007 |
| IBM xSeries 346 |
64 |
Y |
3600 |
Intel Xeon |
Suse Linux |
DB2 UDB 8.2 |
08/15/2005 |
HP Integrity Superdome |
32 |
N |
1600 |
Itanium2 |
Windows 2003 |
Microsoft SQL Server |
05/21/2007 |
| Sun Fire E25K |
72 |
N |
1800 |
UltraSPARC IV+ |
Solaris 10 |
Oracle 10g |
04/09/2007 |
| HP ProLiant BL25p |
64 |
Y |
2600 |
AMD Opteron 285 |
Red Hat Enter. Linux 4 |
Oracle 10g |
06/08/2006 |
| Unisys ES7000/one |
16 |
N |
1600 |
Itanium2 |
Windows 2003 |
Microsoft SQL Server |
09/08/2006 |
| HP rx8640 |
16 |
N |
1600 |
Itanium2 |
Windows 2003 |
Oracle 10g |
05/14/2007 |
| Unisys ES7000 Orion |
32 |
N |
1600 |
Itanium2 |
Windows 2003 |
Microsoft SQL Server |
05/05/2006 |
| IBM p595 |
64 |
N |
1900 |
POWER 5 |
AIX 5L V5.3 |
Oracle 10g |
03/01/2006 |
| Sun Fire E25K |
72 |
N |
1500 |
UltraSPARC IV+ |
Solaris 10 |
Oracle 10g |
01/27/2006 |
| HP Superdome |
64 |
N |
1600 |
Itanium2 |
HP-UX 11.i V2 |
Oracle 10g |
01/18/2006 |
Complete benchmark results may be found at the TPC benchmark website http://www.tpc.org.
Benchmark Description
The TPC-H benchmark is a performance benchmark established by the
Transaction Processing Council (TPC) to demonstrate Data
Warehousing/Decision Support Systems (DSS). TPC-H measurements are
produced for customers to evaluate the performance of various DSS
systems. These queries and updates are executed against a standard
database under controlled conditions. Performance projections and
comparisons between different TPC-H Database sizes (100GB, 300GB,
1000GB, 3000GB and 10000GB) are not allowed by the TPC.
TPC-H is a data warehousing-oriented, non-industry-specific benchmark
that consists of a large number of complex queries typical of decision
support applications. It also includes some insert and delete activity
that is intended to simulate loading and purging data from a warehouse.
TPC-H measures the combined performance of a particular database
manager on a specific computer system.
The main performance metric reported by TPC-H is called the TPC-H
Composite Query-per-Hour Performance Metric (QphH@SF, where SF is the
number of GB of raw data, referred to as the scale factor). QphH@SF is
intended to summarize the ability of the system to process queries in
both single and multi user modes. The benchmark requires reporting of
price/performance, which is the ratio of QphH to total HW/SW cost plus
3 years maintenance. A secondary metric is the storage efficiency,
which is the ratio of total configured disk space in GB to the scale
factor.
Disclosure Statement:
Sun Fire X4500 cluster 38,672.4 QphH@3000GB, $29.39 USD $/QphH@3000GB, avail
10/12/07; IBM eServer xSeries 346 cluster 54,465.9 QphH@3000GB, 32.34 USD
$/QphH@3000GB, avail 8/15/05. TPC-H, QphH, $/QphH tm of Transaction Processing
Performance Council (TPC). More info www.tpc.org.
Results Summary SF3000 (SF3000 = 3000GB) benchmark
| Audited Results |
| |
Database Size: |
3000 GB (Scale Factor 3000) |
| |
TPC-H Composite: |
38,672.4 QphH@3000GB |
| |
Price/performance: |
$29.39 USD $/QphH@3000GB |
| |
Available: |
October 12, 2007 |
| Number of Systems: |
10 Sun Fire X4500 |
| Total Number Processors: |
20 |
| Processor/MHz of Server: |
AMD Dual Core Opteron Model 285 2.6 GHz |
| Storage: |
218.3 Terabytes of disk |
| Database: |
DB2 Release 9.1 |
| Operating System: |
Solaris 10 |
| Total 3 year Cost: |
$1,136,536 USD |
| Other Performance Metrics |
| |
TPC-H Power: |
51,320.0 |
| |
TPC-H Throughput: |
29,141.8 |
| |
Database Load Time: |
3 hours 39 minutes |
Tuesday Oct 16, 2007
IBM just published a somewhat funny TPC-H results. IBM used 32 (4-core
Power6 p570) systems in a clustered TPC-H. Some funny things:
- Why 32 4-core systems instead of clustering eight 16-core systems?
Both configurations are built from the same 4RU 4-core unit.
- Why no IBM Power6 single-system TPC-H results? No stand-alone 16-core, 8-core, 4-core POWER6 results? Maybe they just don't stand on their own when you look at the performance?
- Why did they use 96 x 36.4GB drives on 31 systems and 96 x 73.4GB drives only on server14?
- Why did they use the smallest 36.4GB drives for most drives in the system?
- If the un-discounted server hardware price for thirty-two 4-core systems is $7,042,378usd, what is the price of one 4-core system?
- If the un-discounted server hardware price of $7,042,378usd, and 128 cores, what is the un-discounted price per core when configured in a 4-core system with 32GB?
Disclosure statement
IBM TPC-H 10000GB result on the IBM System p6 570 of 343,551.2 QphH@10000GB ($32.89usdd $/QphH@10000GB, avail. 4/15/2008) on a 32-node cluster of 4-core p570 (each with 2 POWER6 4.7 GHz processor chips, 4 cores, 8 threads) and 32GB of memory per node running DB2 Warehouse 9.5 on AIX 5L V5.3. Total disk capacity was 110,489.27 GB in a IBM Totalstorage DS4800 storage subsystem (using 36.4GB drives on 31 nodes and 73.4 GB drives on server 14) and 10Gigabit Ethernet for cluster interconnect.
Source: http://www.tpc.org; Results current as of 10/15/07.
Monday Jun 04, 2007
The Sun Fire X4100 M2 has 50% better price performance than the HP DL585.
This benchmark result demonstrates that the Sun Fire X4100 M2, powered by 2 dual-core 3.0GHz Opteron, improves upon Sun's previously published world-record
$/performance result at 300GB. The Sun Fire X4100 M2 is the only 1U system ever submitted for a TPC benchmark at the 300GB scale-factor.
The Sun Fire X4100 M2 achieved the best price-performance among all systems
at 300GB. It improved upon Sun's previous world-record price-performance, achieved by the Sun Fire X4200, by 6%.
Note all of this detail, and the very different ways in which results are marketed with the IBM POWER6 post.
The Sun Fire X4100 M2 achieved a 55% QphH@300GB improvement upon previously
published 2-socket Single-core RevE Sun Fire X4200 result, i.e., 7641 QphH@300GB versus 4936 QphH@300GB.
Specifically, Sun, using its Sun Fire X4100 M2 server achieved a
$/QphH@300GB of $5.89, whereas the Sun Fire X4200 achieved a $/QphH@300GB
of $6.29. The latter result was submitted on June 23, 2006.
TPC-H @300GB Performance Results (sorted by $/QphH
for single (non-clustered) systems:
$/QphH = $/QphH@300GB TPC-H Price/Performance metric (smaller is better)
QphH = QphH@300GB TPC-H Composite Metric (bigger is better)
Disk Data Ratio is the ratio of the total number of gigabytes of
configured storage to the scale factor
number of gigabytes (smaller is better)
| System |
Sockets/
Cores/
Threads CPU GHz |
QphH |
Price/
QphH
|
Price
in
currency
|
DBMS
|
Available |
Disk
Data
Ratio
|
Cluster |
Sun X4100 M2
|
And why SUN ashamed m9000 result in TPC-H or Guine...
Triffids: Sun holds the official World Record 100...
As I know 64-core Power6 system was released ...
The p570 4-core and 8-cores 16-cores have been out...
'...Walmart which is said to have half a terabyte....
Single 16-cores system can't get top 10 result, wh...