Portworx operates typically within less than 3% overhead of the underlying storage hardware.

Note that Portworx recommends the following:

  • Minimum resources per server:
    • 4 CPU cores
    • 4 GB RAM
  • Recommended resources per server:
    • 12 CPU cores
    • 16 GB RAM
    • 128 GB Storage
    • 10 GB Ethernet NIC

Examples of Portworx performance as measured by fio

The following graphs show the results of running fio against the underlying baremetal hardware and comparing it to the performance of a Portworx volume that used the underlying hardware for storage provisioning. The graphs show the overhead, or delta, between running the same test on the raw volume and on a PX volume.

In this example, the following Intel server was used: Intel® Wildcat Pass R2312WTTYS 2U from PCSD - Product Collaboration Systems Division

  • Intel® Wildcat Pass R2312WTTYS 2U
    • 2U rack mountable server
    • 2x Intel® Xeon® processors E5-2650 v3 (25M Cache, 2.30 GHz)
    • 500GB SATA 6Gb/s 7200 RPM 2.5” hard drive
    • 120GB Intel® DC S3500 series (Wolfsville) SAS 6Gb/s 2.5” SSD
    • supports up to 12x 3.5” hot-swap drives and 2x 2.5” hot-swap drives
    • 4x 8GB 2133MHz PC4-17000 ECC RDIMM
    • Matrox G200e (Emulex) On-Board Video
    • It also has an Intel® ethernet controller i350 1Gbe dual-port on-board and IPMI 2.0
  • Software
    • Docker version 1.12
    • Centos 7.1
    • PX-Enterprise v1.0.8

Random read performance overhead

Perf Read

Random write performance overhead

Perf Write

mysql performance overhead

In this example, we measure the performance as measured by running a mysql workload against the baremetal server and then against a PX volume on that same server. Perf mysql

Containerized NoSQL Workloads: Cassandra performance gains with running PX-Enterprise

In this example, we show how PX-Enterprise’s network-optimized 3-way replication out-performs Cassandra’s 3-way replication when running on a 3-node cluster. We compared the performance between the following two configuration and ran these tests on the same servers as the tests above.

  • PX-Enterprise replication factor set to 1 and Cassandra replication factor set to 3. (Legend: P1C3 in the diagram below)
  • PX-Enterprise replication factor set to 3 and Cassandra replication factor set to 1. (Legend: P3C1 in the diagram below)

The results demonstrate that running with PX-Enterprise for Cassandra workloads provide significant gains. PX-Enterprise’s breakthrough performance for containerized workloads along with the cloud-scale data protection and data services make it a compelling container data services infrastructure for Cassandra and other no-sql workloads

The Read OPS/sec and Write OPS/sec improvements graphs show how running with PX-Enterprise’s three-node replication deliver a significantly better OPS/sec than running with Cassandra’s three-node replication. This PX-Enterprise performance is also made possible because PX container software stack intelligently leverages NVMe SSDs to deliver high OPS/sec and low latencies.

Cassandra with PX-Enterprise - Read OPS/sec improvements

Cassandra Reads Ops

Cassandra with PX-Enterprise - Write OPS/sec improvements

Cassandra Writes Ops

The latency graphs below demonstrate the network-optimized replication performance of PX-Enterprise as it accelerates cassandra performance by delivering IO at very low latencies to the Cassandra Container

Cassandra with PX-Enterprise - Read Latency improvements

Cassandra Read Lats

Cassandra with PX-Enterprise - Write Latency improvements

Cassandra Write Lats

Edit this page