06-27-2016, 06:08 AM
(06-26-2016, 06:52 PM)ssvb Wrote: How do you measure these 130 Watts for Xeon? How do you measure the current draw for the Pine64? Also isn't maxing at around roughly 84,000 - 105,000 requests per second in every test where you did real measurements a little bit suspicious? Wouldn't it point to the network possibly being the bottleneck rather than the CPU?
Other than this, thanks for the interesting results.
Good Questions,
So let me give you a few details. For measuring current draw, I am using a few devices.
USB Power: DORK USB Digital Multimeter - https://www.amazon.com/gp/product/B00J3J...UTF8&psc=1
AC Power: P3 International P4460 Kill A Watt Usage Monitor - https://www.amazon.com/P3-International-...ill+a+watt
AC Power: Cyberlink UPS
As for testing of the actual throughput capacity for Redis, I am using Redis-Benchmark to provide as close to equal comparison against both devices. I have also run it both locally each device, and across the network to compare and ensure that I do not have network bottlenecks in the way. My back end network is all CAT 6 wiring through a single data center grade DLink 48 port gigabit switch.
Since using Redis-Benchmark locally also technically uses the local ethernet chipset, I have set processor affinity for eth0 to CPU 0, and each Redis shard is then set for it's own affinity to a single CPU core as well.
A single core on the Pine64 can deliver approximately 28,000 request per second, compared to a single core on the Xeon processor delivering approximately 105,000. The Xeon is hyperthreaded giving me a possible 23 usable threads (reserving 1 for network), and the Pine64 is 3 usable threads (reserving 1 for network).
Hope that all make sense?
