1. REPORTING BRICKS High Performance and Scalability through commodity kit Tony Rogerson, SQL Server MVP @tonyrogerson sqlblogcasts.com/blogs/tonyrogerson tonyrogerson@torver.net

2. Agenda What’s the Paradigm? Scale out Commodity kit Redundancy through boxes What throughput? Pound for Pound Commodity SSD V Server SSD Practical Usage

3. Paradigm – Scale Out NoSQL (rather None-Relational) model Multiple nodes on cheap kit It breaks it gets binned Distributed Data/Loading Dryad, Hadoop, Cassandra etc. Relational (ATOMIC [durability]) model True Scale out Volt-DB (inexpensive, open source), Teradata (varies) Scale up or Federated Scale out SQL Server, SQL Azure, Oracle etc.

4. Dryad http://research.microsoft.com/en-us/projects/Dryad/

5. Hadoop - Mapreduce http://www.infoq.com/articles/data-mine-cloud-hadoop

6. Teradata http://www.teradata.com/tdmo/v07n01/Tech2Tech/AskTheExpert/BenefitsOf Fallback.aspx

7. Federation (SQL Azure) http://tinyurl.com/34eew2w Scale out (sort of) but no single data store for BI queries across the “federation”. Each “Federation” is a separate instance of the database

8. WHAT’S THE PROBLEM? Why are the majority of RDBMS slow?

9. Traditional RDMS – ACID (Durability) Write-ahead Logging (WAL) Synchronous Write Request/FlushFileBuffers completes only when data is stable on media This kills write performance on rotational disks! SSD’s burn out when intensively written to (aka the transaction log!)

10. Traditional RDMS – ACID (Consistency) The transaction (BEGIN TRAN….COMMIT/ROLLBACK) is all or nothing Across multiple instances requires three phase commit (3pc) This kills write performance “period” Federation a fix?

11. Read Performance? Data is always fragmented Table joins cause out of sequence access from disk OLAP is usually larger chunks OLTP is small chunks Rotational Disks suffer from head positioning latency (seek latency) in milliseconds usually 2 – 8 Read-ahead Manager assists when data is contiguous In memory access is blistering because virtually no access latency for random access (the predominate access pattern of a rdms) Access mechanism and algorithms based around rotational disk technology going back decades

12. REPORTING BRICKS A method for cost efficient scale out

13. Jim Gray CyberBricks From Terraserver research (first Terabyte scale SQL Server database – 1997) http://research.microsoft.com/apps/pubs/default.aspx?id= 64151 (Barclay, Gray, Chong 2004) http://research.microsoft.com/apps/pubs/default.aspx?id= 64151 Bunch of cheap SATA disks in JBOD or RAID configuration RAPS (Reliable array of partitioned servers) Commodity kit!

14. Redundancy thru boxes SAN Active Node Passive Node Queries TraditionalReporting Bricks £lot’s Commodity Queries Load Balancer £2K Lots of disks and cache

15. What throughput? Rotational Disk is slow – high seek latency SAS, SATA and FC protocols all have baggage Commodity SSD – heavy same place writing burns it out Reduced lifetime for persistent writes Fusion IO SSD Geared to spread across the Nand – ok on heavy writes but expensive Directly plugged into PCI – always the best answer!

16. Benchmarks Demo IOMeter (100GB file) 64KByte random Read 8KByte random Read SQL Server 2008 R2 Adventure Works 54GB Backup speed Query speeds Multi-Core Single-Core (MAXDOP) Single-Core/Dual-Core through processor Affinity

17. Commodity box GRUNT: £154.16 - Gigabyte GA-890FXA-UD7 AMD 890FX (Socket AM3) PCI-Express DDR3 Motherboard £170.20 - AMD Phenom II X6 Six Core 1090T Black Edition 3.20GHz (Socket AM3) £123.25 - 8GB Team Xtreem LV DDR3 PC3-16000 (9-11-9-27) Dual Channel Low-Voltage kit £123.25 - 8GB Team Xtreem LV DDR3 PC3-16000 (9-11-9-27) Dual Channel Low-Voltage kit Sub-Total: 570.86 IO: £108.36 - 80GB OCZ Vertex 2 SATA II 2.5" SSD Solid State Disk (285MB/sec read 275MB/sec write) £442.85 - 240GB OCZ IBIS 3.5-inch HSDL High-Speed Data Link SSD (read 740MB/s - write 720MB/s) £442.85 - 240GB OCZ IBIS 3.5-inch HSDL High-Speed Data Link SSD (read 740MB/s - write 720MB/s) Sub-Total: 994.06 TOTAL:£1,564.92 16GB DDR3 memory 6 cores 447GB of storage capable of 100% random reads: over 1GBytes (19,757 64KByte per second) with latency of 6.6 milliseconds Over 660MBytes (84,619 8KByte per second with latency of 3.02 milliseconds)

18. Server box HP DL385 G7 AMD Opteron™ 6176 (2.3GHz/12-core/12MB/80W) FIO Processor Kit approx 2300 64GB PC3-10600R memory 4 x HP 16GB (1x16GB) Quad Rank x4 PC3-8500 (DDR3-1066) Registered CAS-7 Memory Kit (500666-B21) approx 575 each, 2300 HP 512MB P-Series Battery Backed Write Cache Upgrade approx 209 HP 146GB 6G SAS 15K SFF (2.5-inch) Dual Port Enterprise 3yr Warranty Hard Drive 512547-B21 approx 255 each HP 600GB 6G SAS 10K rpm SFF (2.5-inch) Dual Port Enterprise 3y Wty Hard Drive 581286-B21 approx 539 each 64GB DDR3 memory 12 cores What cost for IO subsystem? What are your needs? Note, 15Krpm SAS is around 175 IOs/sec of semi-random read with a latency of 2 – 5 milliseconds. SAS Drive Performance: http://www.adaptec.com/blog/2006/07/26/sas-drive-performance/

19. Suggested Usage Nothing that has intensive same page/file writes e.g. the transaction log, type 1 slowing changing dimensions Perfect for incremental inserts e.g. type 2 slowing changing dimensions, transactions, orders etc. Archived data through partitioning

20. Keeping the copies in sync ETL Denali HADRON Commodity Queries Load Balancer £2K OLTPETL Multicast

21. Denali HADRON Windows Failover Cluster Virtual Network Name Connections (Primary Replica) Primary ReplicaSecondary Replica Read only Connections (Secondary Replica) Read only Connections (Secondary Replica) Availability Groups seen as Cluster Groups in WFC Standalone SQL Instances not a cluster install Primary replica is connected via VNN Secondary replicas connect directly to standalone instance (this is your commodity boxes!) Allows for DASD – no shared storage required

22. Summary and Questions Commodity kit is a real option Almost like building your own appliance Standard build; image machine Fault tolerance is part of the already redundant infrastructure Licencing costs can spiral but can be offset against the cost of the redundancy requirements of server kit You can always use servers at the end of the day – it’s a method afterall!