Oracle TimesTen In-Memory Database Performance on SPARC T4-2

Posted by Brian on Oracle Blogs See other posts from Oracle Blogs or by Brian
Published on Mon, 1 Oct 2012 16:23:34 +0000 Indexed on 2012/10/01 21:45 UTC
Read the original article Hit count: 536

Filed under:

The Oracle TimesTen In-Memory Database is optimized to run on Oracle's SPARC T4 processor platforms running Oracle Solaris 11 providing unsurpassed scalability, performance, upgradability, protection of investment and return on investment. The following demonstrate the value of combining Oracle TimesTen In-Memory Database with SPARC T4 servers and Oracle Solaris 11:

On a Mobile Call Processing test, the 2-socket SPARC T4-2 server outperforms:

  • Oracle's SPARC Enterprise M4000 server (4 x 2.66 GHz SPARC64 VII+) by 34%.

  • Oracle's SPARC T3-4 (4 x 1.65 GHz SPARC T3) by 2.7x, or 5.4x per processor.

Utilizing the TimesTen Performance Throughput Benchmark (TPTBM), the SPARC T4-2 server protects investments with:

  • 2.1x the overall performance of a 4-socket SPARC Enterprise M4000 server in read-only mode and 1.5x the performance in update-only testing. This is 4.2x more performance per processor than the SPARC64 VII+ 2.66 GHz based system.

  • 10x more performance per processor than the SPARC T2+ 1.4 GHz server.

  • 1.6x better performance per processor than the SPARC T3 1.65 GHz based server.

In replication testing, the two socket SPARC T4-2 server is over 3x faster than the performance of a four socket SPARC Enterprise T5440 server in both asynchronous replication environment and the highly available 2-Safe replication. This testing emphasizes parallel replication between systems.

Performance Landscape

Mobile Call Processing Test Performance

System Processor Sockets/Cores/Threads Tps
SPARC T4-2 SPARC T4, 2.85 GHz 2 16 128 218,400
M4000 SPARC64 VII+, 2.66 GHz 4 16 32 162,900
SPARC T3-4 SPARC T3, 1.65 GHz 4 64 512 80,400

TimesTen Performance Throughput Benchmark (TPTBM) Read-Only

System Processor Sockets/Cores/Threads Tps
SPARC T3-4 SPARC T3, 1.65 GHz 4 64 512 7.9M
SPARC T4-2 SPARC T4, 2.85 GHz 2 16 128 6.5M
M4000 SPARC64 VII+, 2.66 GHz 4 16 32 3.1M
T5440 SPARC T2+, 1.4 GHz 4 32 256 3.1M

TimesTen Performance Throughput Benchmark (TPTBM) Update-Only

System Processor Sockets/Cores/Threads Tps
SPARC T4-2 SPARC T4, 2.85 GHz 2 16 128 547,800
M4000 SPARC64 VII+, 2.66 GHz 4 16 32 363,800
SPARC T3-4 SPARC T3, 1.65 GHz 4 64 512 240,500

TimesTen Replication Tests

System Processor Sockets/Cores/Threads Asynchronous 2-Safe
SPARC T4-2 SPARC T4, 2.85 GHz 2 16 128 38,024 13,701
SPARC T5440 SPARC T2+, 1.4 GHz 4 32 256 11,621 4,615

Configuration Summary

Hardware Configurations:

SPARC T4-2 server
2 x SPARC T4 processors, 2.85 GHz
256 GB memory
1 x 8 Gbs FC Qlogic HBA
1 x 6 Gbs SAS HBA
4 x 300 GB internal disks
Sun Storage F5100 Flash Array (40 x 24 GB flash modules)
1 x Sun Fire X4275 server configured as COMSTAR head

SPARC T3-4 server
4 x SPARC T3 processors, 1.6 GHz
512 GB memory
1 x 8 Gbs FC Qlogic HBA
8 x 146 GB internal disks
1 x Sun Fire X4275 server configured as COMSTAR head

SPARC Enterprise M4000 server
4 x SPARC64 VII+ processors, 2.66 GHz
128 GB memory
1 x 8 Gbs FC Qlogic HBA
1 x 6 Gbs SAS HBA
2 x 146 GB internal disks
Sun Storage F5100 Flash Array (40 x 24 GB flash modules)
1 x Sun Fire X4275 server configured as COMSTAR head

Software Configuration:

Oracle Solaris 11 11/11
Oracle TimesTen 11.2.2.4

Benchmark Descriptions

TimesTen Performance Throughput BenchMark (TPTBM) is shipped with TimesTen and measures the total throughput of the system. The workload can test read-only, update-only, delete and insert operations as required.

Mobile Call Processing is a customer-based workload for processing calls made by mobile phone subscribers. The workload has a mixture of read-only, update, and insert-only transactions. The peak throughput performance is measured from multiple concurrent processes executing the transactions until a peak performance is reached via saturation of the available resources.

Parallel Replication tests using both asynchronous and 2-Safe replication methods. For asynchronous replication, transactions are processed in batches to maximize the throughput capabilities of the replication server and network. In 2-Safe replication, also known as no data-loss or high availability, transactions are replicated between servers immediately emphasizing low latency. For both environments, performance is measured in the number of parallel replication servers and the maximum transactions-per-second for all concurrent processes.

See Also

Disclosure Statement

Copyright 2012, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Results as of 1 October 2012.

© Oracle Blogs or respective owner

Related posts about /Benchmark