SPEC SFS(R)2014_swbuild Result WekaIO : WekaIO Matrix SPEC SFS2014_swbuild = 500 Builds (Overall Response Time = 3.06 msec) =============================================================================== Performance =========== Business Average Metric Latency Builds Builds (Builds) (msec) Ops/Sec MB/Sec ------------ ------------ ------------ ------------ 50 0.9 25001 397 100 1.1 50004 794 150 1.4 75006 1191 200 1.7 100007 1588 250 3.4 125009 1986 300 2.5 150011 2383 350 3.0 175012 2780 400 4.0 200013 3177 450 5.7 225012 3574 500 8.8 248839 3953 =============================================================================== Product and Test Information ============================ +---------------------------------------------------------------+ | WekaIO Matrix | +---------------------------------------------------------------+ Tested by WekaIO Hardware Available Not Applicable Software Available April 2017 Date Tested June 2017 License Number 4553 Licensee Locations San Jose, California WekaIO Matrix Software solves the challenge of scaling high performance file workloads from tens to thousands of server clients. Matrix Software transforms a cluster of compute servers (on-premises or in AWS) into a globally shared, POSIX compliant file system that delivers industry leading performance and scale for enterprise file workloads and HPC environments. Matrix Software makes it simple to install and manage hundreds of compute nodes from a single management console. For peak performance needs, additional Matrix instances can be dynamically added to scale performance, while capacity can be scaled independently within the compute nodes. WekaIO Matrix is flash native providing the highest performance to applications, and its integrated tiering mechanism automatically moves cold data to any S3 or Swift compliant object store (on-premises or public cloud), while maintaining data locality to the applications. All data is presented as a single global namespace. WekaIO Matrix is ideal for technical computing workloads such as EDA design, Big Data analytics, software development, genomic sequencing, financial analytics, media rendering and HPC research. The software can be deployed natively in a hyperconverged mode with zero additional footprint, or as a dedicated storage appliance. Because it is a software only solution it is up to 80% less costly than external flash based NAS appliances. This test platform is a hyperconverged implementation. Solution Under Test Bill of Materials ===================================== Item No Qty Type Vendor Model/Name Description ---- ---- ---------- ---------- ---------- ----------------------------------- 1 60 AWS EC2 Amazon r3.8xlarge Amazon r3.8 instances are optimized Instance instance for memory-intensive applications and offer lower price per GiB of RAM. Features: High Frequency Intel Xeon E5-2670 v2 (Ivy Bridge) Processors, 640GB of SSD Storage, Support for Enhanced Networking Configuration Diagrams ====================== 1) sfs2014-20170620-00019.config1.png (see SPEC SFS2014 results webpage) Component Software ================== Item Name and No Component Type Version Description ---- ------------ ------------ ------------ ----------------------------------- 1 Hyperconverg MatrixFS 2.5.2 WekaIO Matrix is a distributed and ed Server File System parallel POSIX file system that Nodes runs on any SSD enabled commodity server or cloud compute instance and forms a single cluster. The file system presents a single high performance, scalable global namespace to the applications running in the cluster. 2 Hyperconverg Operating CENTOS 6.7 The operating system on the ed Server System hyperconverged server was 64-bit Nodes CENTOS Version 6.7. Hardware Configuration and Tuning - Virtual =========================================== +----------------------------------------------------------------------+ | SR-IOV | +----------------------------------------------------------------------+ Parameter Name Value Description --------------- --------------- ---------------------------------------- SR-IOV Enabled Enables CPU virtualization technology Hardware Configuration and Tuning Notes --------------------------------------- SR-IOV was enabled in the EC2 instance BIOS. No additional hardware tuning was required. Software Configuration and Tuning - Virtual =========================================== +----------------------------------------------------------------------+ | Hyperconverged Server Nodes | +----------------------------------------------------------------------+ Parameter Name Value Description --------------- --------------- ---------------------------------------- Jumbo Frames 9000 Enables up to 9000 bytes of Ethernet Frames Software Configuration and Tuning Notes --------------------------------------- The MTU is required and valid for all environments and workloads. Service SLA Notes ----------------- Not applicable Storage and Filesystems ======================= Item Stable No Description Data Protection Storage Qty ---- ------------------------------------- ------------------ -------- ----- 1 MatrixFS Enabled Amazon EC2 15+2 Yes 1 r3.8xlarge instances used as shared file system Number of Filesystems 1 Total Capacity 24176 GiB Filesystem Type MatrixFS Filesystem Creation Notes ------------------------- A single WekaIO Matrix file system was created and distributed evenly across all 60 instances in the Amazon cluster. Data was protected to an 15+2 failure level. All data and metadata is distributed evenly across the cluster. Storage and Filesystem Notes ---------------------------- WekaIO MatrixFS was created and distributed evenly across all 60 instances in the Amazon cluster. The deployment model is as a hyperconverged architecture where both storage and application services are run on the same infrastructure. Each EC2 instance has 32 vCPU, 244GiB of memory and 2x320GB (total 640GB) of SSD local to the instance. Two cores of the available 32 (6.25%) were provisioned with MatrixFS, the remaining 30 cores were available for application usage. Each instance had 13GB (5%) of memory assigned to WekaIO. Transport Configuration - Virtual ================================= Item Number of No Transport Type Ports Used Notes ---- --------------- ---------- ----------------------------------------------- 1 10GbE Virtual 60 Interface Notes NIC Transport Configuration Notes ----------------------------- WekaIO Matrix utilizes the shared 10GbE Virtual NIC on each r3.8xlarge instance. 1x10GbE Virtual NIC per EC2 instance for a total of 60. Applications and storage run on the same network. Switches - Virtual ================== Total Used Item Port Port No Switch Name Switch Type Count Count Notes ---- -------------------- --------------- ------ ----- ------------------------ 1 AWS 10GbE with AWS AWS Switch Notes Enhanced Networking Processing Elements - Virtual ============================= Item No Qty Type Location Description Processing Function ---- ---- -------- -------------- ------------------------- ------------------- 1 120 vCPU AWS EC2 Intel(R) Xeon(R) CPU Processing Function core r3.8xlarge E5-2670 v2 @ 2.50GHz instance Processing Element Notes ------------------------ Each amazon instance had 32 vCPUs. WekaIO used only 2 cores per instance. Memory - Virtual ================ Size in Number of Description GiB Instances Nonvolatile Total GiB ------------------------- ---------- ---------- ------------ ------------ AWS EC2 r3.8xlarge 244 60 V 14640 instance memory Grand Total Memory Gibibytes 14640 Memory Notes ------------ WekaIO utilized 13GBytes of memory per instance Stable Storage ============== Each WekaIO instance used the EC2 instance ephemeral drive for stable storage. Data was protected using WekaIO Matrix Distributed Data Protection (15+2). The data is journaled as well as UPS protected accross multiple layers. Solution Under Test Configuration Notes ======================================= The solution under test was a standard WekaIO Matrix enabled cluster in hyperconverged mode. The solution will handle both large file I/O as well as small file random I/O and metadata intensive applications. No specialized tuning is required for different or mixed use workloads. The storage services and client applications share the same instances without the need for any additional dedicated storage instances. Other Solution Notes ==================== None Dataflow ======== The EC2 instances are both the load generators and the storage nodes. All of the instances accessed the same WekaIO Matrix shared file system that was distributed and protected across all of the EC2 instances. Other Notes =========== None Other Report Notes ================== None =============================================================================== Generated on Wed Mar 13 16:47:50 2019 by SpecReport Copyright (C) 2016-2019 Standard Performance Evaluation Corporation