1. Tag line, tag line Perforce Benchmark with PAM over NFS, FCP & iSCSI Bikash R. Choudhury

2. © 2008 NetApp. All rights reserved. 2 Perforce Testing with Performance Acceleration Module  Goal –Compare Perforce benchmark results with and without PAM –Compare Perforce benchmark results over NFS v/s iSCSI v/s FCP  Measured performance of metadata on NetApp storage with and without PAM –Entire feature set not considered –Tests conducted under controlled environment

3. © 2008 NetApp. All rights reserved. 3 Executive Summary  Result –40% to 90% READ performance improvements with PAM –For READ performance, NFS slightly faster than iSCSI and FCP without PAM  Application is single threaded; iSCSi/FCP on ext3 with 4k block size is less effective than NFS with 64k blocks  Host side cache gets flushed; NFS (file access) is faster than iSCSI (blocks) served out of WAFL cache –For WRITE performance, iSCSI is 7x faster than NFS –Typical Perforce workload : 70% READ, 30% WRITE

4. © 2008 NetApp. All rights reserved. 4 Deltas Benchmark – READ workload 4 SYNC TestINTEGRATE Test DIR Test 0 10 20 30 40 50 60 0.2 0.4 0.6 0.8 Time in Seconds 88% 75% 0.4 0.8 1.2 1.6 36% NFS Time in Seconds 0 0.2 0.4 1 0.6 0.8 0 20 40 80 60 2.5 0 0.5 1 2 1.5 iSCSI Time in Seconds 91% 76% 43% Response time improvements are averages across 2, 6, and 3 tests for Dir, Integrate and Sync test respectively 0 10 20 30 40 50 60 0 0.2 0.4 0.6 0.8 Time in Seconds 96%85% 0 0.4 0.8 1.2 1.6 61% FCP Time in Seconds FAS 3070 With PAM FAS 3070 without PAM

5. © 2008 NetApp. All rights reserved. 5 Branchsubmit Benchmark – WRITE workload  The test does "submit" of the change list action (p4 submit -c ) that holds approximately a dozen locks on the database tables for update purposes. –FCP  11 seconds – Elapsed time (time taken for each command to complete)  13500 files/sec – Commit rate (rate @ which files are written to disk) –iSCSI  14 seconds – Elapsed time  14,000 files/sec – Commit rate –NFS  50 seconds – Elapsed Time  2000 files/sec – Commit rate

6. © 2008 NetApp. All rights reserved. 6 Perforce Architecture

7. © 2008 NetApp. All rights reserved. 7 Perforce Architecture  Metadata DB – Files that compose the Perforce database  Journal Files - A record of all transactions performed by the server after the last checkpoint was created  Versioned Files (Depot) - Store the file revisions.  LOG – Contain the error output files

8. © 2008 NetApp. All rights reserved. 8 Test Descriptions  Deltas Benchmark (READ test) –Used NetApp Eng. IT real production data to generate the p4 database and journal files for this test –DIR, INTEGRATE, SYNC tests generate READ workload  INTEGRATE / DIR scans/parses/reads the different revisions of the code from the p4 database with and without use of locks  SYNC test downloads selected file(s) from the DEPOT to their client workspace –Odd and Even-numbered Integrates use related data  Related data already in NetApp cache (memory + PAM) for even- numbered integrates –Demonstrates great performance improvement when data is already present in NetApp cache  Branchsubmit Benchmark (WRITE Test) –Used Perforce’s Reference Dataset –Heavy WRITEs with limited READs; Single threaded  Sets exclusive locks on files for writes  Faster writes release locks for user read requests

9. © 2008 NetApp. All rights reserved. PAM Settings  There are three modes of operations for PAM –Default –Metadata –Low Priority  Mainly used in RANDOM read workloads  The actual application data is seldom reused in a timely manner – hence caching helps!! –The random nature of the p4 workload tends to use more metadata

10. © 2008 NetApp. All rights reserved. 10 NetApp Storage ControllerFAS3070 – AA Cluster OSDataONTAP Release 7.3 Cache8 GB NetApp Drive Shelves One shelf with fourteen 300Gb 15k drives on each head Drive Access Protocol ISCSI NFS – Both over 1 gigabit interface FCP PAM1 PCI Slot (16GB) NetApp Storage Specifications

11. © 2008 NetApp. All rights reserved. 11 Perforce Host Specifications OSRedhat Enterprise Linux 5 update 2 Kernel2.6.18-88.el5xen #1 SMP NFS mount options rw,nfsvers=3,bg,hard,rsize=65536,wsize=65536, acregmin=3600,acregmax=3600,acdirmin=7200, acdirmax=7200,proto=tcp,nointr,nolock,timeo=600, retrans=5 Initiator for iSCSISoftware initiator Memory32Gb Processor(s)8 way Intel Xeon quad Core 2.00GHz

12. © 2008 NetApp. All rights reserved. 12 Hardware Connections  Two filesystems mounted over NFSv3 from one FAS3070 head with 1 PAM  Two iSCSI LUNs mounted from another FAS3070 head with 1 PAM card  Two FCP LUNs mounted from same FAS3070 head with 1 PAM card  Both NFS & iSCSI connections are over single dedicated 1Gb Ethernet  The FCP target and initiator were connected back-to- back  The NFS filesystems, iSCSI and FCP LUNs were mounted to one single host running Perforce 2007.3 on RHEL5update2.

13. © 2008 NetApp. All rights reserved. Key Takeaways - PAM  PAM is needed where you want to reach high performance –With few spindles in workloads –With small blocks –Random read workload –A lot of metadata READ ops

14. © 2008 NetApp. All rights reserved. 14 Thank You 14 © 2008 NetApp. All rights reserved.