Benchmark Results

Though the systems are equipped with similar components, some notable observations can be made. Each benchmark was executed three times to verify the accuracy of our results. All ratios are calculated using the Dell R730 as baseline (=100%).

OLAP 95pct Response Time
(Lower is better)
Power
(Lower is better)
Throughput
(Higher is better)
Concurrency Facebook
Leopard
Intel
Decathlete v2
Facebook
Leopard
Intel
Decathlete v2
Facebook
Leopard
Intel
Decathlete v2
5 114% 111% 99% 99% 94% 117%
10 108% 105% 99% 98% 96% 109%
25 96% 94% 100% 101% 100% 116%
50 98% 56% 103% 110% 101% 112%
100 96% 49% 110% 149% 103% 119%
250 98% 67% 105% 144% 103% 120%
250 95% 67% 106% 144% 103% 120%
250 95% 67% 105% 143% 102% 120%
250 90% 62% 106% 143% 103% 121%

An interesting result: the Dell outperforms both Open Compute servers when it comes to energy efficiency. It is good to remember that the PSU used for the Facebook server is not optimal (it should get its power from a power shelf). Leopard is very close, and gets a slightly better performance mark, while Decathlete is a respectable 20% faster, but uses 40% more power in the process.

Next, we tested with our real-world Elasticsearch benchmark. Due to ES's internal queuing algorithm, the throughput and response time can vary wildly when it drops a 'heavy' request to allow it to pass many smaller ones, and we've seen the inverse happen as well. These tests were executed five times to confirm ensure the consistency of most results.

ElasticSearch 95pct Response Time
(Lower is better)
Power
(Lower is better)
Throughput
(Higher is better)
Concurrency Leopard Decathlete v2 Leopard Decathlete v2 Leopard Decathlete v2
5 115% 73% 107% 106% 96% 104%
10 88% 88% 75% 94% 101% 101%
25 74% 26% 90% 98% 118% 165%
50 96% 41% 95% 104% 100% 153%
100 97% 74% 98% 108% 107% 124%
200 103% 85% 97% 112% 108% 129%
200 96% 75% 100% 110% 108% 130%
200 89% 66% 95% 112% 110% 137%
200 96% 80% 95% 108% 113% 128%
250 92% 70% 97% 113% 101% 121%

Whereas the Dell and Leopard performed comparably in the OLAP test, ElasticSearch tests results are in favor of the Leopard. The throughput and response times are slightly better and Leopard uses slightly less power resulting in a tangibly better performance/watt with a sub optimal power supply. The Decathlete system gets the best scores on the board again, but this time the power usage increase is relatively modest: 8 to 13 percent.

Benchmark Configuration: Leopard Under Stress Visiting Facebook's Labs & Alternative OCP Standards
Comments Locked

26 Comments

View All Comments

  • Kevin G - Tuesday, April 28, 2015 - link

    Excellent article.

    The efficiency gains are apparent even using suboptimal PSU for benchmarking. (Though there are repeated concurrency values in the benchmarking tables. Is this intentional?)

    I'm looking forward to seeing a more compute node hardware based around Xeon-D, ARM and potentially even POWER8 if we're lucky. Options are never a bad thing.

    Kind of odd to see the Knox mass storage units, I would have thought that OCP storage would have gone the BackBlaze route with vertically mount disks for easier hot swap, density and cooling. All they'd need to develop would have been a proprietary backplane to handle the Kinetic disks from Seagate. Basic switching logic could also be put on the backplane so the only external networking would be high speed uplinks (40 Gbit QSFP+?).

    Speaking of the Kinetic disks, how is redundancy handled with a network facing drive? Does it get replicated by the host generating the data to multiple network disks for a virtual RAID1 redundancy? Is there an aggregator that handles data replication, scrubbing, drive restoration and distribution, sort of like a poor man's SAN controller? Also do the Kinetic drives have two Ethernet interfaces to emulate multi-pathing in the event of a switch failure (quick Googling didn't give me an answer either way)?

    The cold storage racks using Blu-ray discs in cartridges doesn't surprise me for archiving. The issue I'm puzzled with is the process how data gets moved to them. I've been under the impression that there was never enough write throughput to make migration meaningful. For a hypothetical example, by the time 20 TB of data has been written to the discs, over 20 TB has been generated that'd be added to the write queue. Essentially big data was too big to archive to disc or tape. Parallelism here would solve the throughput problem but that get expensive and takes more space in the data center that could be used for hot storage and compute.

    Do the Knox storage and Wedge networking hardware use the same PDU connectivity as the compute units?

    Are the 600 mm wide racks compatible use US Telecom rack width equipment (23" wide)? A few large OEMs offer equipment in that form factor and it'd be nice for a smaller company to mix and match hardware with OCP to suit their needs.
  • nils_ - Wednesday, April 29, 2015 - link

    You can use something like Ceph or HDFS for data redundancy which is kind of like RAID over network.
  • davegraham - Tuesday, April 28, 2015 - link

    Also, Juniper Networks has an ONIE-compliant OCP switch called the OCX1100 which is the only Tier1 switch manufacturer (e.g. Cisco, Arista, Brocade) to provide such a device.
  • floobit - Tuesday, April 28, 2015 - link

    This is very nice work. One of the best articles I've seen here all year. I think this points at the future state of server computing, but I really wonder if the more traditional datacenter model (VMware on beefy blades with a proprietary FC-connected SAN) can be integrated with this massively-distributed webapp model. Load-balancing and failovering is presumably done in the app layer, removing the need for hypervisors. As pretty as Oracle's recent marketing materials are, I'm pretty sure they don't have an HR app that can be load-balanced on the app layer in alongside an expense app and an ERP app. Maybe in another 10 years. Then again, I have started to see business suites where they host the whole thing for you, and this could be a model for their underlying infrastructure.
  • ggathagan - Tuesday, April 28, 2015 - link

    In the original article on these servers, it was stated that the PSU's were run on 277v, as opposed to 208v.
    277v involves three phase power wiring, which is common in commercial buildings, but usually restricted to HVAC-related equipment and lighting.
    That article stated that Facebook saved "about 3-4% of energy use, a result of lower power losses in the transmission lines."
    If the OpenRack carries that design over, companies will have to add the cost of bringing power 277v to the rack in order to realize that gain in efficiency.
  • sor - Wednesday, April 29, 2015 - link

    208 is 3 phase as well, generally 3x120v phases, with 208 tapping between phases or 120 available to neutral. Its very common for DC equipment. 277 to the rack IS less common, but you seemed to get hung up on the 3 phase part.
  • Casper42 - Monday, May 4, 2015 - link

    3 phase restricted to HVAC?
    Thats ridiculous, I see 3 Phase in DataCenters all the time.
    And Server vendors are now selling 277vAC PSUs for exactly this reason that FB mentions. Instead of converting the 480v main to 220 or 208, you just take a 277 feed right off the 3 phase and use it.
  • clehene - Tuesday, April 28, 2015 - link

    You mention a reported $2 Billion in savings, but the article you refer to states $1.2 Billion.
  • FlushedBubblyJock - Tuesday, April 28, 2015 - link

    One is the truth and the other is "NON Generally Accepted Accounting Procedures" aka it's lying equivalent.
  • wannes - Wednesday, April 29, 2015 - link

    Link corrected. Thanks!

Log in

Don't have an account? Sign up now