![]() In-Memory OLTP is the premier performance technology of SQL Server which significantly increases performance of transactional workloads, compared with traditional (disk-based) database technology. VM type must be generation 2 and VM version must be 8.0 or newer.Both host and VM guest OS must be Windows Server 2016 or newer.Note: to use the new Hyper-V large scale VMs, the follow conditions must be met: Virtual Machine Virtual Processor Support Physical (Host) Logical Processor Support Below is the comparison between Windows Server 2012/2012 R2 and Windows Server 2016 for Hyper-V scalability on a per VM basis: Windows Server 2016 increases the scalability for Hyper-V virtual machines (VMs), with support for up to 240 virtual processors and 12 terabytes of memory. In-Memory Processing Performance Numbers Comparison Hyper-V Large-Scale VM Support in Windows Server 2016 Compared with 358K TPS performance with the physical host, Hyper-V VM delivers ~95% of what a physical host can do. We achieved over 340K OLTP Transactions per Second (TPS) when running the OLTP workload in a single large-scale Hyper-V VM. The in-memory database size is approximately 4TB with durable, fully logged tables – some of those tables have over 5 billion rows. We used BenchCraft, an internal Microsoft tool, to run an OLTP (Online Transaction Processing) workload against the in-memory database. SQL Server In-Memory OLTP Performance Comparison Finally, we detail the hardware and software setup used in the experiment. We then recap the increased scalability for VMs with Hyper-V in Windows Server 2016, in-memory transaction processing support in SQL Server 2016, and the benchmark workload we used to obtain these performance numbers. The performance in the VM was >95% of the performance on a physical server.īelow, we first present our findings, comparing the performance of a physical host versus a Hyper-V large-scale VM. The result: 343,000 transactions per second using an order processing workload with a 4 terabyte in-memory database, running in a VM with 5.5 terabytes of memory and 128 virtual processors. In this post, we highlight the performance of in-memory transaction processing at scale using SQL Server 2016 running in a Windows Server 2016 Hyper-V VM. ![]() With Windows Server 2016, Microsoft has significantly bumped up the Hyper-V Virtual Machine (VM) scale limit to embrace new scenarios such as running e-commerce large in-memory databases for Online Transaction Processing (OLTP) and Data Warehousing (DW) purposes. This post was authored by Liang Yang, Principal Performance Engineer on the Hyper-V team and Jos de Bruijn, Senior Program Manager on the SQL Server team.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |