SPECsfs97_R1.v3 Result

Performance

Throughput (ops/sec) Response (msec) 992 0.7 2004 0.9 3036 1.0 4044 1.2 5029 1.2 6050 1.3 7086 1.5 8102 1.7 9125 2.3 10120 3.4

Configuration

LG Type	LG1
LG Model	Dell PowerEdge 1850
Number and Type Processors	Intel(R) dual Xeon(TM) CPU 3.00GHz
Memory Size	2GB
Operating System	Red Hat Enterprise Linux ES release 4
Compiler	pre-compiled binary
Compiler Options	N/A
Network Type	1 Gigabit Eth interface

Testbed Configuration
LG #	LG Type	Network	Target File Systems	Notes
1-4	LG1	1	/vol1, /vol2, /vol3, /vol4, /vol5, /vol6, /vol7, /vol8, /vol101, /vol102, /vol103, /vol104, /vol105, /vol106, /vol107, /vol108,	N/A

Other Notes

• The system under test is an ONStor Bobcat NAS Gateway in front of a
• 3PAR InServ S800 Storage Server.
•  
• The ONStor Bobcat NAS Gateway has no NVRAM anywhere in the filer.
• All updates are written to external stable storage on 3PAR Storage
• Server before acknowledging the client. Memory caches
• within an ONStor NAS Gateway are effectively write-through caches.
•  
• The ONStor Bobcat NAS Gateway contains two BCM1250 processors each with
• two cores (total 4 CPUs). All network protocol and filesystem operations
• are performed by these processors.
•  
• The ONStor Bobcat NAS Gateway has one network controller with two Gigabit
• ethernet connections, all connected to the same network. A custom FPGA
• is used to calculate the CRC for TCP. Jumbo frames were not used.
•  
• The ONStor Bobcat NAS Gateway has one disk controller with two 2 Gbps FC
• ports. All ports are managed by one core of a PMC-Sierra RM9200 CPU with
• 512 MB of memory and a QLOGIC ISP2312 FC controller.
•  
• The two FC controller ports on the ONStor Bobcat NAS Gateway were
• connected to a 16 port fibre channel switch (McData Sphereon 4500).
• Each 3PAR Controller Node had two ports connected to the same fibre
• channel switch.
•  
• The 3PAR S800 Storage Server is a fibre-channel-attached, block-level
• storage array. The 3PAR S800 was configured as a single array with two
• 2,400 MHz 3PAR Controller Nodes.
• Each Controller Node of the 3PAR InServ S800 includes 8 GB of
• data cache (16 GB total). The InServ S800 has an additional 2 GB
• of control cache (CPU memory) per Controller Node.
• Write-caching occurs in the disk subsystem only.
•  
• There are redundant lead-acid batteries supporting each 3PAR
• Controller Node. These batteries power the node during a power
• failure, saving all cache contents to an internal drive.
• Booting after a power failure initiates a recovery process that
• recovers cache contents from the internal drives.
•  
• The 3PAR Controller Nodes are configured with "common provisioning groups"
• which configure and dedicate portions of physical storage from a common
• pool of undedicated capacity upon write operations.
•  
• The ONStor NAS Gateway created 16 filesystems (or "volumes" in ONStor
• terminology). Each volume was written to eight TPVV's, "Thin
• Provisioned Virtual Volume", on the 3PAR InServ.
• TPVVs were configured to grow using a RAID-0 relationship and to
• stripe across 60 disks.
•  
• Automatic snapshot scheduling was disabled and data cache read-ahead
• was disabled on the NAS Gateway.
•  
• ONStor, the ONStor logo, EverON, and STOR-FS are trademarks of ONStor, Inc.
•  
• 3PARdata, the 3PAR logo, 3PAR, InServ and InForm are trademarks of 3PARdata, Inc.
•  
• Other trademarks are the property of their respective holders.
•  

Generated on Mon Aug 29 15:43:18 2005 by SPEC SFS97 HTML Formatter
Copyright © 1997-2004 Standard Performance Evaluation Corporation

First published at SPEC.org on 29-Aug-2005