SPECstorage™ Solution 2020_eda_blended Result
Copyright © 2016-2024 Standard Performance Evaluation Corporation
|
SPECstorage™ Solution 2020_eda_blended ResultCopyright © 2016-2024 Standard Performance Evaluation Corporation |
| WEKAIO, Inc. | SPECstorage Solution 2020_eda_blended = 6310 Job_Sets |
|---|---|
| WEKA - Public Cloud Reference | Overall Response Time = 0.87 msec |
|
|
| WEKA - Public Cloud Reference | |
|---|---|
| Tested by | WEKAIO, Inc. | Hardware Available | February 2024 | Software Available | February 2024 | Date Tested | February 2024 | License Number | 4553 | Licensee Locations | Campbell, CA USA |
The WEKA Data Platform is purpose-built to seamlessly and sustainably deliver speed, simplicity, and scale that meets the needs of modern enterprises and research organizations without compromise. Its advanced, software-defined architecture supports next-generation workloads in virtually any location with cloud simplicity and on-premises performance.
| Item No | Qty | Type | Vendor | Model/Name | Description |
|---|---|---|---|---|---|
| 1 | 40 | AWS Virtual Machine | AWS | Standard i3en.24xlarge | WEKA storage backends - AWS Standard i3en.24xlarge Virtual Machine (96 vCPUs, 768 GiB memory, 100 Gbps networking) |
| 2 | 40 | AWS Virtual Machine | AWS | Standard c5n.18xlarge | Amazon Linux clients with WEKA POSIX-compliant filesystem driver - AWS Standard C5n.18xlarge Virtual Machine (72 vCPUs, 192 GiB memory, 100 Gbps networking) |
| Item No | Component | Type | Name and Version | Description |
|---|---|---|---|---|
| 1 | WekaFS | File System | Version 4.2.8.66 | The WEKA filesystem (WekaFS) redefines storage solutions with its software-only approach and addresses common storage challenges by removing performance bottlenecks, making it suitable for environments requiring low latency, high performance, and cloud scalability. |
| 2 | Weka Backend Node | Storage OS | Amazon Linux v2 kernel 5.10 | Operating System (OS) for 40 storage virtual machines using AWS i3en.24xlarge instances |
| 3 | Clients | Client OS | Amazon Linux v2 kernel 5.10 | Operating System (OS) for 40 client virtual machines using AWS c5n.18xlarge instances |
| Component Name | Parameter Name | Value | Description |
|---|---|---|
| Enhanced Networking | Enabled | Both c5n.18xlarge and i3en.24xlarge instances have 100 Gbps connectivity |
None
| Networking | Parameter Name | Value | Description |
|---|---|---|
| Jumbo Frames | 9001 | WekaFS recommended MTU for AWS. |
| num_cores | 7 | WekaFS mount option to designate the number of frontend cores to allocate for the client. |
The single filesystem was attached via a single mount per client. The mount string used was "mount -t wekafs -o net=eth1 -o net=eth2 -o net=eth3 -o net=eth4 -o net=eth5 -o net=eth6 -o net=eth7 -o num_cores=7 -o readahead_kb=4096 -o mgmt_ip=10.0.3.153 internal-spec-boni-lb-344769224.us-east-1.elb.amazonaws.com/default /mnt/weka" The mount specifies that 7 WEKA front ends (cores) were used on the clients.
None
| Item No | Description | Data Protection | Stable Storage | Qty |
|---|---|---|---|---|
| 1 | WEKA Filesystem with 1.66 PiB of usable storage | WEKA 16+2 distributed data protection | Amazon EC2 7TB NVMe Drives | 320 |
| Number of Filesystems | 1 | Total Capacity | 1.66 PiB | Filesystem Type | WekaFS |
|---|
Each storage backend has eight 7TB Amazon EC2 NVMe drives attached to it, which are dedicated to the WEKA filesystem created. The storage cluster consisted of 40 storage servers with a single WEKA filesystem created in the cluster. Each client mounted the WEKA filesystem with a single mount.
None
| Item No | Transport Type | Number of Ports Used | Notes |
|---|---|---|---|
| 1 | 100 Gbps Virtual Nic | 40 | Used by WEKA Backend Server Nodes |
| 2 | 100 Gbps Virtual Nic | 40 | Used by WEKA Frontend Client Nodes |
None
| Item No | Switch Name | Switch Type | Total Port Count | Used Port Count | Notes |
|---|---|---|---|---|---|
| 1 | AWS | 100 Gbps Ethernet with Enhanced Networking | 40 | 40 | Used by WEKA Backend Servers |
| 2 | AWS | 100 Gbps Ethernet with Enhanced Networking | 40 | 40 | Used by WEKA Frontend Clients |
| Item No | Qty | Type | Location | Description | Processing Function |
|---|---|---|---|---|---|
| 1 | 3840 | vCPU | i3en.24xlarge WEKA Backend | 2.5 GHz Intel(R) Xeon(R) Platinum 8259CL processors | WekaFS, Network Communications, Storage Functions |
| 2 | 2880 | vCPU | c5n.18xlarge WEKA Frontend | 3 GHz Intel(R) Xeon(R) Platinum 8124M processors | WekaFS, Network Communications, Storage Functions |
None
| Description | Size in GiB | Number of Instances | Nonvolatile | Total GiB |
|---|---|---|---|---|
| AWS i3en.24xlarge Virtual Machine Memory | 768 | 40 | V | 30720 |
| AWS c5n.18xlarge Virtual Machine Memory | 192 | 40 | V | 7680 | Grand Total Memory Gibibytes | 38400 |
None
WekaFS does not use any internal memory to temporarily cache write data to the underlying storage system. All writes are commited directly to the storage disk, and protected via WekaFS Distributed Data Protection (16+2 in this case). There is no need for any RAM battery protection. In an event of a power failure a write in transit would not be acknowledged.
The system under test consisted of 40 x c5n.18xlarge AWS client virtual machines and 40 x i3en.24xlarge backend virtual machines. Both client and backend have 100Gbps network connectivity.
Entire cloud deployment is automated using Weka Terraform Module. See https://docs.weka.io/install/aws/weka-installation-on-aws-using-terraform for more information.
None
weka debug override list: heartbeat_grace_msecs 20000 heartbeat_timeout_msecs 5000
The solution under test was a standard WekaFS cluster in dedicated server 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. SUT not vulnerable to Spectre or Meltdown (CVE-2017-5754, CVE-2017-5753, CVE-2017-5715).
Generated on Wed Mar 6 17:45:16 2024 by SpecReport
Copyright © 2016-2024 Standard Performance Evaluation Corporation
