1 / 24

ἑκατόν

ἑκατόν. by Niko Neugebauer. Niko Neugebauer. PASS Evangelist SQL Server MVP SQLPort ( http://www.sqlport.com ) founder & leader BITuga ( http://www.bituga.pt ) co -founder 15+ years in IT. HeKATON. HEK-A-TON, HEK-A-TON, HEK-A-TON. HekAton. ἑκατόν – means 100 in Greek

emilia
Download Presentation

ἑκατόν

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ἑκατόν by NikoNeugebauer

  2. NikoNeugebauer • PASS Evangelist • SQL Server MVP • SQLPort (http://www.sqlport.com) founder & leader • BITuga(http://www.bituga.pt) co-founder • 15+ years in IT

  3. HeKATON HEK-A-TON, HEK-A-TON, HEK-A-TON

  4. HekAton • ἑκατόν – means 100 inGreek • Targeted to improve OLTP performance, 100 Times

  5. Conceptionally? • Imagine that you have a number of CPU steps to perform a typical OLTP action • Optimize it 100 times by removing obstacles like latches and parallelize it • Yes, you will need start from the bottom and from the very beginning?

  6. Hardware Trends • Look at the CPU speed increase • Look at the Memory Prices • You can’t buy a SQL Server Enterprise License for a price of a TB • Think, think, think 

  7. New generation DB Hekaton

  8. History Sybase SQL Server 1.0 SQL Server 11.0 2012 Hardware Cheap IO & Memory Bound Pages 8K • 1980 (1989) • Hardware Expensive • CPU Bound • Pages 8K

  9. Hekaton • In-Memory Database • Multi-Core Awareness and Optimizations • xVelocity compression algorithm (hint: ColumnStore) • No Pages (no more splits, allocations, etc) • No Locks, No Latches + different Concurrency Control • StreamInsight (no more 8K’s) • Hash Index (no more b-trees) • Existing T-SQL can be reused

  10. Hekaton • Highly scalable concurrency control mechanism • Lock-free data structures

  11. Hekaton • ACID compliant • Optimized for extreme Transaction Processing scenarios like • Financial Services • Online Gambling • There are customers who are using it NOW

  12. Integrated into the DataBase Engine Hekaton

  13. Particular Features • Snapshot_Isolation ONLY • No support for LOB data types • No Triggers • AlwaysOn Support

  14. features • Durable Tables • Non-Durable Tables • TempDB is used inside of the Hekaton, in-memory • Shares memory with Buffer Pool, but has its own space

  15. Architecture • Different space allocation for memory buffer • The very same transaction log, but with fewer writes • Different filegroups • Different treatment for Indexes • A lot of new, different stuff 

  16. HEKATON It actually looks like a …

  17. Programability • Create table dbo.Hekaton( • Id int primary key hash with (bucketcount = 65535), • Nome varchar(50) ) WITH (MEMORY_OPTIMIZED = ON, DURABILITY = SCHEMA_AND_DATA ); GO

  18. T-SQL Stored Procs: • Uses C as internal intermediate presentation, and then compiles into native code • Atomic blocks • Can’t reference non-hekaton tables

  19. T-SQL Programability • Create procedure dbo.HekatonNow • WITH NATIVE_COMPILATION BEGIN select name from dbo.Hekaton; END GO

  20. Details • Uses StreamInsight • No actual updates, but deletes & inserts

  21. UTils • Migration from the normal DB tables to Hekaton • Stored Procedures Migration to Hekaton

  22. WHEN ? Next major version of SQL Server

  23. BUT • Isn’t it too fast ? • – No, there is no such concept as too fast. (as long as it does not create other problems)

  24. Thank you

More Related