By Lisa Coleman
Two years after launching the Direct Access File System (DAFS) initiative, Network Appliance is rolling out the first DAFS product this month that will accelerate performance for IBM DB2, Oracle 8i and 9i, and Sybase database environments running on its filers.
The improvement to transaction processing performance using DAFS and network-attached storage (NAS) may rival iSCSI, according to one analyst. "The big knock on NAS has been the performance, primarily in transaction processing. But now you have a whole new ballgame," says Randy Kerns, senior partner at the Evaluator Group.
The DAFS Database Accelerator 1.0 uses virtual interface (VI) technology over a Gigabit Ethernet interconnect to support larger data workloads on existing hardware used for database environments.
The accelerator is available with Network Appliance's F800 series filers running its proprietary DataOnTap 6.2 software, which now supports the DAFS protocol. However, users must purchase a DAFS protocol license, and the filer must be equipped with an Emulex GN9000/VI host bus adapter (HBA). The accelerator will not work with NetApp's F700 series. A database server-attach kit, which will include an Emulex GN9000/VI HBA and DAFS accelerator driver software, will also be available.
DAFS is a file-access protocol based on NFS version 4. The protocol is designed specifically for high-performance file sharing in data-center environments. It uses a memory-to-memory I/O architecture and runs on Fibre Channel, Gigabit Ethernet, and InfiniBand.
The accelerator derives its speed from reduced CPU overhead on the database server since VI is implemented in the HBA, according to David Dale, marketing manager for Network Appliance and co-chair of the DAFS Collaborative.
"The goal is to leapfrog direct-attached or SAN-attached performance for high-intensity online transaction processing [OLTP] workloads," explains Dale, who cites recent company tests measuring CPU overhead reduction on the database server.
Network Appliance claims it measured 70ms CPU overhead operation on a database server using the DAFS accelerator. The test compared the DAFS implementation to the following systems: direct-attached storage (DAS) using a volume manager (113ms); DAS with a local file system (89ms); and raw access to DAS (76ms).
The test used a 4-CPU Sun E3000 running Solaris. The OLTP workload included 66% reads and 34% writes using 4KB transfers and asynchronous I/O. Dale credits the Gigabit Ethernet and the Emulex HBAs for the overhead reduction in the DAFS system. Dale also cites single-filer performance of 325 MBps out of a single filer and up to 30,000 I/Os per second.
The test results cited above were performed in Network Appliance's labs using a test similar to the Transaction Processing Performance Council (TPC-C) instruction mix.
"The tests don't necessarily tell you about overall performance," says Kerns, "but they tell you about the instantaneous response time. Those are probably fairly accurate numbers, but that doesn't tell you how it's going to work in your environment. But those are stunning numbers," he says.
The company also performed a TPC-C test to measure performance and price/performance. The test ran on a 16-CPU Fujitsu Siemens server, Network Appliance's F820 filers, the DAFS database accelerator software, and Sybase. The total amount of storage used was about 8TB in a RAID-4 configuration.
The test results yielded 112,286.46 transactions per minute (tpmC) at $13.44 per tpmC.
This implementation of DAFS did not require any changes to the application--something that DAFS opponents criticize the protocol for requiring. In future implementations of DAFS, however, application modifications will have to be made. "The disadvantage is that you need changes in the application, but the advantage is that you get huge performance boosts," says Dale.
The DAFS Collaborative was founded by Network Appliance and Intel and consists of 87 companies. The collaborative published DAFS specification v1.0 and API specification v1.0 in September and November 2001, respectively. After completing the specifications, the collaborative disbanded into three separate initiatives. One is pursuing the DAFS specification's progress through the IETF standards body, and another group is part of the DAFS Implementer's Forum within the Storage Networking Industry Association (SNIA).
The third group is participating in the Direct Access Transport (DAT) collaborative, which is a spin-off of the DAFS transport working group. The DAT collaborative is writing a set of transport-independent, platform-independent APIs that exploit remote direct memory access (RDMA) capabilities of InfiniBand, the VI architecture, and iWARP-RDMA over 10Gbit Ethernet.
"Think about this. InfiniBand native transfer is also VI," says Kerns, so DAFS may be the future when we get InfiniBand-based servers and InfiniBand-based storage.