[db tech showcase Tokyo 2017] D21: ついに Red Hat Enterprise Linuxで SQL Serverが使える！～Dr. KによるSQL Server 2017 Linux版性能検証速報～ by Winテクノロジ株式会社熊澤幸生

1. ついに Red Hat Enterprise Linuxで SQL Serverが使える！～Dr. KによるSQL Server 2017 Linux版性能検証速報～ WinTechnology Corporation 技術フェロー特別役員熊澤幸生

2. Copyright© WinTechnology Corporation. All Rights Reserved. レッドハット、Winテクノロジ、HPE共同検証この検証は、レッドハット株式会社、Winテクノロジ株式会社、日本ヒューレット・パッカード株式会社が共同で実施したものです。 • 日本ヒューレット・パッカードの ProLiant DL360 Gen9サーバーで • レッドハットのRed Hat Enterprise Linux をOSとし • Microsoft SQL Server 2017 CTP 2.1版を使って • Winテクノロジが検証したものです。

4. Copyright© WinTechnology Corporation. All Rights Reserved. SQLOS とは ? • SQL Server 7.0 / SQL Server 2000 で UMS (ユーザモド・スケジューラ) として誕生 • UMS を SQL Server 2005 で機能拡張し、 SQLOS が誕生 • 二つの DLL (SQLDK.DLL & SQLOS.DLL) から構成されるエンジン • Windows OS 上のサービスとは異なる • 多くのデータ構造から構成される • SQLOS は抽象化層 • 開発者向けに SQLOS API を提供 • オペレーティングシステムと SQL Server を関連付けするインターフェース • RDBMS から独立している • スケーラブル、かつ、NUMA 機能をフルに活用する • サイズは小さく、かつ、最適化されている • Windows API を利用して機能拡張を行っている • マイクロソフトで最も優秀な開発技術者の集団でチーム構成 • Red Hat Enterprise Linux / Ubuntu に移植し動作確認済み • SQL Server Engineering Team : Slava Oks を中心に推進

5. Copyright© WinTechnology Corporation. All Rights Reserved. マルチプラットフォームアーキテクチャ Host Extension mapping to OS system call (I/O, Memory, CPU Scheduling) Win 32 API SQLOS API SQL Platform Abstraction Layer (SQL PAL) Performance Critical code SQLOS v2 Non-performance Critical code Win32 API Windows OS Red Hat Enterprise Linux

6. Copyright© WinTechnology Corporation. All Rights Reserved. SQL Server 2017 CTP 2.1 Linux版検証環境 SQL Server用サーバー DL360 Gen9 Xeon E5 V4 2640 2.4GHz 2P 20C 256GB PCIe NVMe 1.6TB x 1 NVDIMM 8GB x 1 Red Hat Enterprise Linux 7.3 SQL Server 2017 CTP 2.1 SQL Server用サーバー DL360 Gen9 Xeon E5 V4 2640 2.4GHz 2P 20C 256GB PCIe NVMe 1.6TB x 1 NVDIMM 8GB x 1 Windows Server 2016 SQL Server 2017 CTP 2.1 負荷かけ用サーバー DL360 Gen9 Xeon E5 V4 2640 2.4GHz 2P 20C 256GB Windows Server 2016 同じトランザクションを実行して性能を比較

7. Copyright© WinTechnology Corporation. All Rights Reserved. 負荷テストモデル • 各 SQLStressTool.exe は 200 Threads を起動し、データベースに接続後、240 秒間連続してトランザクションを発行するスレッドの処理多重度を、1,200 / 1,400 / 1,600 と変化させ処理能力の変化を測定する総処理トランザクション数を、Transactions /sec に変換後比較する • データベースは同一構造を持ち、データベース数は、CPU ソケットごとに 4 つ作成し、最大 8 DBとする DB1 . . . . . . . SQLStressTool DB2 SQLStressTool DB3 SQLStressTool DB8 SQLStressTool

8. Copyright© WinTechnology Corporation. All Rights Reserved. 負荷テストツールのパラメータ • SQLStressTool.exe は、事前に定義したトランザクションミックスをランダムに発行する <SQLSTRESS> <CONFIGURATIONPARAMS> <RUNTIME>240</RUNTIME> <SQLSERVER>172.18.217.111</SQLSERVER> <DATABASENAME>Northwind</DATABASENAME> <THREADSPERDATABASE>200</THREADSPERDATABASE> <USEWARMUP>1</USEWARMUP> <WARMUPSLEEP>5</WARMUPSLEEP> <USEPOOLING>1</USEPOOLING> <MAXPOOLCONNECTIONS>1100</MAXPOOLCONNECTIONS> <THINKTIMEMIN>1000</THINKTIMEMIN> <THINKTIMEMAX>2000</THINKTIMEMAX> <VERBOSE>1</VERBOSE> <REPORTSTATUSINTERVAL>5</REPORTSTATUSINTERVAL> <CONNECTIONBEHAVIOR>1</CONNECTIONBEHAVIOR> <DISCONNECTFREQUENCY>10</DISCONNECTFREQUENCY> <BATCHTIMEOUT>60</BATCHTIMEOUT> <CONNECTTIMEOUT>35</CONNECTTIMEOUT> <USERNAME>sa</USERNAME> <PASSWORD>P@ssw0rd123</PASSWORD> <USETRUSTED>0</USETRUSTED> <FAIL_THRESHOLD_PERCENT>50</FAIL_THRESHOLD_PERCENT> <NETLIB>TCP</NETLIB> </CONFIGURATIONPARAMS> <WORKLOAD> <WORKITEM> <ID>0</ID> <QUERY><![CDATA[exec GetCustInfo]]></QUERY> <WEIGHT>10</WEIGHT> </WORKITEM> <WORKITEM> <ID>1</ID> <QUERY><![CDATA[exec NewCustOrder]]></QUERY> <WEIGHT>20</WEIGHT> </WORKITEM>

9. Copyright© WinTechnology Corporation. All Rights Reserved. トランザクションミックス Transaction Name 処理概要 Weight 参照・追加・更新テーブル名 1 2 3 4 GetCustInfo 顧客情報の照会 10 Customers NewCustOrder 顧客からの受注処理 20 Orders Order Details GetCustOrderDetails 顧客受注明細照会 8 Order Details Customers GetCustOrderHistory 顧客受注履歴の照会 2 Products Order Details Orders Customers UpdCustOrderShippedDate 出荷実績日時の更新 5 Orders UpdCustOrderRequireDate 顧客希望納期の更新 5 Orders GetCustProductOrderHistory 顧客別・商品別受注履歴照会 3 Products Order Details Orders Customers GetCustContact 顧客担当窓口の検索 10 Customers GetProductInfo 商品情報の検索 13 Products Suppliers GetSupplierInfo 商品納入先の検索 13 Suppliers SalesByCategoryByYear カテゴリー別年次売上明細の照会 1 Orders Products Categories GetEmployeeInfo 従業員情報の検索 10 Employees Total 100

10. Copyright© WinTechnology Corporation. All Rights Reserved. 負荷テストツールの実行ログ 15:52:52 INFO-LoadConfigurationInformation: Loading configuration from: Northwind_Stress_Demo_1.xml 15:52:53 INFO-LoadConfigurationInformation: XML Configuration loaded. 15:52:53 INFO-ReportConfigParams: ********************************************************************* SQL Server: 172.18.217.111 Database Name: Northwind Trusted Security: OFF (sa/P@ssw0rd123) Threads Per Database: 200 Number of Databases: 1 Starting Database: 0 Run Time: 240 (seconds) Reporting Interval: 5 (seconds) Think Time (min): 1000 (milliseconds) Think Time (max): 2000 (milliseconds) Connection Ramp Up Time: 5 (milliseconds) Connection Timeout: 35 (seconds) Batch Timeout: 60 (seconds) Failed Threshold: 70 (percent) Pooling Behavior: OFF (Persistant Connections) Verbose Error Reporting: True ********************************************************************* 15:52:53 INFO-StartStressRun: Starting worker threads. 15:52:53 INFO-StartStressRun: Warm up used, starting one thread every 5 milliseconds. 15:52:56 INFO-StartStressRun: Worker thread creation complete. 200 started. 15:52:58 INFO-MonitorThreadMain: Duration: 5 (sec) Succeeded: 361 Failed: 0 AvgRT: 9 (ms) 15:53:03 INFO-MonitorThreadMain: Duration: 10 (sec) Succeeded: 1021 Failed: 0 AvgRT: 9 (ms) 15:53:08 INFO-MonitorThreadMain: Duration: 15 (sec) Succeeded: 1670 Failed: 0 AvgRT: 9 (ms) 15:53:13 INFO-MonitorThreadMain: Duration: 20 (sec) Succeeded: 2316 Failed: 0 AvgRT: 14 (ms)

11. Copyright© WinTechnology Corporation. All Rights Reserved. 物理NUMA とソフトNUMA • 物理 NUMA の認識 • SQL Server on Windows は、Win32 API により、稼働する環境の物理 NUMA 数 (CPU ソケット数) を入手可能 • SQL Server は、サービス起動時に、物理 NUMA の最適化を実施する • SQL Server detected 2 sockets with 10 cores per socket and 10 logical processors per socket 20 total logical processors • SQL Server on Linux は、認識手段を持たないために、稼働する環境のCPU コア数を入手する • SQL Server は、サービス起動時に、複数 CPU コアを持つ、SMP 環境と認識する • ソフト NUMA とは • SQL Server 2016 からサポート開始 (automatic soft-NUMA disabled パラメータにより無効・有効の設定) • Automatic soft-NUMA was enabled because SQL Server has detected hardware NUMA nodes with greater than 8 physical cores. • 物理 NUMA 環境、SMP 環境の両方で利用可能

12. Copyright© WinTechnology Corporation. All Rights Reserved. SQLOS Scheduler on Windows parent_ node_ id scheduler_ id cpu_id current_ tasks_ count runnable_ tasks_ count current_ workers_ count active_ workers_ count work_ queue_ count pending_ disk_io_ count 0 0 0 7 3 14 7 0 0 0 1 1 6 2 12 5 0 0 0 2 2 3 0 11 3 0 0 0 3 3 10 7 10 10 0 0 0 4 4 4 0 13 3 0 0 1 5 5 2 0 14 2 0 0 1 6 6 7 3 15 6 0 0 1 7 7 5 2 13 5 0 0 1 8 8 5 1 14 5 0 0 1 9 9 4 0 17 2 0 0 2 10 64 4 1 15 4 0 0 2 11 65 4 0 16 3 0 0 2 12 66 5 2 15 5 0 0 2 13 67 6 2 16 6 0 0 2 14 68 4 0 16 3 0 0 3 15 69 2 0 16 2 0 0 3 16 70 6 1 20 5 0 0 3 17 71 3 1 13 3 0 0 3 18 72 3 0 16 3 0 0 3 19 73 5 1 16 4 0 0 95 26 292 86 0 0

13. Copyright© WinTechnology Corporation. All Rights Reserved. SQL Start-up Log on Windows In-Memory OLTP initialized on highend machine. Lock partitioning is enabled. Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. Node configuration: node 3: CPU mask: 0x00000000000003e0:1 Active CPU mask: 0x00000000000003e0:1. Node configuration: node 2: CPU mask: 0x000000000000001f:1 Active CPU mask: 0x000000000000001f:1. Node configuration: node 1: CPU mask: 0x00000000000003e0:0 Active CPU mask: 0x00000000000003e0:0. Node configuration: node 0: CPU mask: 0x000000000000001f:0 Active CPU mask: 0x000000000000001f:0. This instance of SQL Server last reported using a process ID of 8472 at 2017/07/12 17:19:33 (local) 2017/07/12 8:19:33 (UTC). The maximum number of dedicated administrator connections for this instance is '1' Buffer pool extension is already disabled. Automatic soft-NUMA was enabled because SQL Server has detected hardware NUMA nodes with greater than 8 physical cores. Default collation: SQL_Latin1_General_CP1_CI_AS (日本語 1041) Machine supports memory error recovery. SQL memory protection is enabled to recover from memory corruption. Using conventional memory in the memory manager. Detected 262014 MB of RAM. SQL Server detected 2 sockets with 10 cores per socket and 10 logical processors per socket 20 total logical processors; using 20 logical processors based on SQL Server licensing. Command Line Startup Parameters: -s "MSSQLSERVER" Registry startup parameters: <nl/> -d H:¥Program Files¥Microsoft SQL Server¥MSSQL14.MSSQLSERVER¥MSSQL¥DATA¥master.mdf -e H:¥Program Files¥Microsoft SQL Server¥MSSQL14.MSSQLSERVER¥MSSQL¥Log¥ERRORLOG -l H:¥Program Files¥Microsoft SQL Server¥MSSQL14.MSSQLSERVER¥MSSQL¥DATA¥mastlog.ldf -T 1204 -T 1222 The service account is 'NT Service¥MSSQLSERVER' Logging SQL Server messages in file 'H:¥Program Files¥Microsoft SQL Server¥MSSQL14.MSSQLSERVER¥MSSQL¥Log¥ERRORLOG'. Authentication mode is MIXED. System Manufacturer: 'HP' System Model: 'ProLiant DL360 Gen9'. Server process ID is 11332. UTC adjustment: 9:00 Microsoft SQL Server 2017 (CTP2.1) - 14.0.600.250 (X64) Enterprise Evaluation Edition (64-bit) on Windows Server 2016 Datacenter 10.0 <X64> (Build 14393: )

14. Copyright© WinTechnology Corporation. All Rights Reserved. SQLOS scheduler on Linux parent_ node_id scheduler_ id cpu_id current_ tasks_count runnable_ tasks_count current_ workers_count active_ workers_count work_ queue_count pending_ disk_io_count 0 0 0 7 3 9 7 0 0 0 1 1 3 0 8 2 0 0 0 2 2 5 1 8 5 0 0 0 3 3 5 2 9 5 0 0 0 4 4 3 0 9 2 0 0 1 5 5 2 0 8 2 0 0 1 6 6 4 0 9 3 0 0 1 7 7 3 0 9 3 0 0 1 8 8 3 0 9 3 0 0 1 9 9 4 0 11 2 0 0 2 10 10 4 1 10 4 0 0 2 11 11 6 1 11 5 0 0 2 12 12 5 1 10 5 0 0 2 13 13 3 0 10 3 0 0 2 14 14 7 3 11 6 0 0 3 15 15 2 0 8 2 0 0 3 16 16 4 0 10 3 0 0 3 17 17 1 0 8 1 0 0 3 18 18 3 0 9 3 0 0 3 19 19 3 0 10 2 0 0 77 12 186 68 0 0

16. Copyright© WinTechnology Corporation. All Rights Reserved. SQL sp_configure on Windows name minimum maximum config_value run_value name minimum maximum config_value run_value access check cache bucket count 0 65,536 0 0lightweight pooling 0 1 0 0 access check cache quota 0 2,147,483,647 0 0locks 5,000 2,147,483,647 0 0 Ad Hoc Distributed Queries 0 1 0 0max degree of parallelism 0 32,767 10 10 affinity I/O mask -2,147,483,648 2,147,483,647 0 0max full-text crawl range 0 256 4 4 affinity mask -2,147,483,648 2,147,483,647 0 0max server memory (MB) 128 2,147,483,647 204,800 204,800 affinity64 I/O mask -2,147,483,648 2,147,483,647 0 0max text repl size (B) -1 2,147,483,647 65,536 65,536 affinity64 mask -2,147,483,648 2,147,483,647 0 0max worker threads 128 65,536 0 0 Agent XPs 0 1 0 0media retention 0 365 0 0 allow polybase export 0 1 0 0min memory per query (KB) 512 2,147,483,647 1,024 1,024 allow update 0 1 0 0min server memory (MB) 0 2,147,483,647 0 16 automatic soft-NUMA disabled 0 1 0 0nested triggers 0 1 1 1 backup checksum default 0 1 0 0network packet size (B) 512 32,767 4,096 4,096 backup compression default 0 1 1 1Ole Automation Procedures 0 1 0 0 blocked process threshold (s) 0 86,400 0 0open objects 0 2,147,483,647 0 0 c2 audit mode 0 1 0 0 optimize for ad hoc workloads 0 1 1 1 clr enabled 0 1 0 0PH timeout (s) 1 3,600 60 60 clr strict security 0 1 1 1polybase network encryption 0 1 1 1 common criteria compliance enabled 0 1 0 0precompute rank 0 1 0 0 contained database authentication 0 1 0 0priority boost 0 1 0 0 cost threshold for parallelism 0 32,767 5 5query governor cost limit 0 2,147,483,647 0 0 cross db ownership chaining 0 1 0 0query wait (s) -1 2,147,483,647 -1 -1 cursor threshold -1 2,147,483,647 -1 -1recovery interval (min) 0 32,767 0 0 Database Mail XPs 0 1 0 0remote access 0 1 1 1 default full-text language 0 2,147,483,647 1,041 1,041remote admin connections 0 1 1 1 default language 0 9,999 3 3remote data archive 0 1 0 0 default trace enabled 0 1 1 1remote login timeout (s) 0 2,147,483,647 10 10 disallow results from triggers 0 1 0 0remote proc trans 0 1 0 0 EKM provider enabled 0 1 0 0remote query timeout (s) 0 2,147,483,647 600 600 external scripts enabled 0 1 0 0Replication XPs 0 1 0 0 filestream access level 0 2 0 0scan for startup procs 0 1 0 0 fill factor (%) 0 100 0 0server trigger recursion 0 1 1 1 ft crawl bandwidth (max) 0 32,767 100 100set working set size 0 1 0 0 ft crawl bandwidth (min) 0 32,767 0 0show advanced options 0 1 1 1 ft notify bandwidth (max) 0 32,767 100 100SMO and DMO XPs 0 1 1 1 ft notify bandwidth (min) 0 32,767 0 0transform noise words 0 1 0 0 hadoop connectivity 0 7 0 0two digit year cutoff 1,753 9,999 2,049 2,049 index create memory (KB) 704 2,147,483,647 0 0user connections 0 32,767 0 0 in-doubt xact resolution 0 2 0 0user options 0 32,767 0 0

18. Copyright© WinTechnology Corporation. All Rights Reserved. sp_configure on Linux name minimum maximum config_value run_value name minimum maximum config_value run_value access check cache bucket count 0 65,536 0 0lightweight pooling 0 1 0 0 access check cache quota 0 2,147,483,647 0 0locks 5,000 2,147,483,647 0 0 Ad Hoc Distributed Queries 0 1 0 0max degree of parallelism 0 32,767 10 10 affinity I/O mask -2,147,483,648 2,147,483,647 0 0max full-text crawl range 0 256 4 4 affinity mask -2,147,483,648 2,147,483,647 0 0max server memory (MB) 128 2,147,483,647 204,800 204,800 affinity64 I/O mask -2,147,483,648 2,147,483,647 0 0max text repl size (B) -1 2,147,483,647 65,536 65,536 affinity64 mask -2,147,483,648 2,147,483,647 0 0max worker threads 128 65,535 0 0 Agent XPs 0 1 1 1media retention 0 365 0 0 allow polybase export 0 1 0 0min memory per query (KB) 512 2,147,483,647 1,024 1,024 allow updates 0 1 0 0min server memory (MB) 0 2,147,483,647 0 16 automatic soft-NUMA disabled 0 1 0 0nested triggers 0 1 1 1 backup checksum default 0 1 0 0network packet size (B) 512 32,767 4,096 4,096 backup compression default 0 1 1 1Ole Automation Procedures 0 1 0 0 blocked process threshold (s) 0 86,400 0 0open objects 0 2,147,483,647 0 0 c2 audit mode 0 1 0 0 optimize for ad hoc workloads 0 1 1 1 clr enabled 0 1 0 0PH timeout (s) 1 3,600 60 60 clr strict security 0 1 1 1polybase network encryption 0 1 1 1 common criteria compliance enabled 0 1 0 0precompute rank 0 1 0 0 contained database authentication 0 1 0 0priority boost 0 1 0 0 cost threshold for parallelism 0 32,767 5 5query governor cost limit 0 2,147,483,647 0 0 cross db ownership chaining 0 1 0 0query wait (s) -1 2,147,483,647 -1 -1 cursor threshold -1 2,147,483,647 -1 -1recovery interval (min) 0 32,767 0 0 Database Mail XPs 0 1 0 0remote access 0 1 1 1 default full-text language 0 2,147,483,647 1,033 1,033remote admin connections 0 1 1 1 default language 0 9,999 0 0remote data archive 0 1 0 0 default trace enabled 0 1 1 1remote login timeout (s) 0 2,147,483,647 10 10 disallow results from triggers 0 1 0 0remote proc trans 0 1 0 0 EKM provider enabled 0 1 0 0remote query timeout (s) 0 2,147,483,647 600 600 external scripts enabled 0 1 0 0Replication XPs 0 1 0 0 filestream access level 0 2 0 0scan for startup procs 0 1 0 0 fill factor (%) 0 100 0 0server trigger recursion 0 1 1 1 ft crawl bandwidth (max) 0 32,767 100 100set working set size 0 1 0 0 ft crawl bandwidth (min) 0 32,767 0 0show advanced options 0 1 1 1 ft notify bandwidth (max) 0 32,767 100 100SMO and DMO XPs 0 1 1 1 ft notify bandwidth (min) 0 32,767 0 0transform noise words 0 1 0 0 hadoop connectivity 0 7 0 0two digit year cutoff 1,753 9,999 2,049 2,049 index create memory (KB) 704 2,147,483,647 0 0user connections 0 32,767 0 0 in-doubt xact resolution 0 2 0 0user options 0 32,767 0 0 xp_cmdshell 0 1 0 0

20. Copyright© WinTechnology Corporation. All Rights Reserved. 負荷テストの実施結果 • Red Hat Enterprise Linux と Windows Server 2016 上の同一ハードウエア環境で、接続ユーザ数を変化させ、240 秒間の OLTP 負荷テストを実施した • Red Hat Enterprise Linux と Windows Server 2016 の処理能力は同等との結果を得ることができた Red Hat Enterprise Linux Windows 1,200 Threads 780.85 Tran/Sec 780.96 Tran/Sec 1,400 Threads 910.91 Tran/Sec 910.70 Tran/Sec 1,600 Threads 1,038.38 Tran/Sec 1,039.53 Tran/Sec

21. Copyright© WinTechnology Corporation. All Rights Reserved. 負荷テスト Windows vs Linux 0 1,000 2,000 3,000 4,000 5,000 6,000 240 Min OLTP 負荷テスト時系列結果 Windows 1,200 Threads Windows 1,400 Threads Windows 1,600 Threads RHEL 7.3 1,200 Threads RHEL 7.3 1,400 Threads RHEL 7.3 1,600 Threads

24. Copyright© WinTechnology Corporation. All Rights Reserved. データ収集スクリプト • 実行コマンド • sqlcmd -S 172.18.217.112 -i "c:¥SQLStressTool¥DataCollect¥First.sql" -o "C:¥DL360GEN9-37¥1600_0705_10300¥First.txt" -w 4000 • sqlcmd -S 172.18.217.112 -i "c:¥SQLStressTool¥DataCollect¥Last.sql" -o "C:¥DL360GEN9-37¥1600_0705_1030¥Last.txt" -w 4000 • 取得スクリプト • First print '== sys.dm_io_virtual_file_stats ==' select * from sys.dm_io_virtual_file_stats(null, null) dbcc sqlperf('sys.dm_os_wait_stats', clear) dbcc sqlperf('sys.dm_os_latch_stats', clear) DECLARE @i int; SET @i = 1; WHILE @i < 5 BEGIN WAITFOR DELAY '00:01:00'; SELECT N'Time',GETDATE() as Date; Print '== sys.dm_os_schedulers ==' select GETDATE(), * from sys.dm_os_schedulers Print '== sys.dm_os_performance_counters ==' select GETDATE(), * from sys.dm_os_performance_counters SET @i = @i + 1; END • Last select * from sys.dm_os_wait_stats select * from sys.dm_io_virtual_file_stats(null, null)

25. Copyright© WinTechnology Corporation. All Rights Reserved. 負荷テスト時の内部動作の比較分析 • Red Hat Enterprise Linux と Windows Server 2016 の負荷テスト実施中の、SQL Server 内部動作の各種データを、それぞれ SSMS から動的管理ビューを実行して、取得分析を行った • SQLOS スケジューラの稼働分析 • SQLOS 内部待ち事象の発生状況分析 • データベースファイルの I/O 分析

26. Copyright© WinTechnology Corporation. All Rights Reserved. 負荷テスト実施時の共有資源とクエリーの調査 • 内部の待ち事象からの考察 • sys.dm_os_wait_stats • SQLOS の待ち事象からシステムの状況を把握する • 何が把握できるか • アプリケーションアーキテクチャの問題点 • メモリー不足 / CPU ボトルネック / ディスクサブシステム帯域不足 • 適切なインデックスの欠落 • データベース I/O 負荷の把握 • sys.dm_io_virtual_file_stats • データベース物理ファイルとログファイルの I/O 発生状況を把握する • パフォーマンスカウンター値からの調査 • sys. dm_os_performance_counters • CPU コア(スケジューラ)のボトルネック調査 • sys.dm_os_schedulers • クエリー実行プランの調査 • Query Store

27. Copyright© WinTechnology Corporation. All Rights Reserved. Windows SQLOS Schedulers 240 Sec 稼働状況 parent_node_ id scheduler_ id cpu_ id preemptive_switches_ count context_switches_ count idle_switches_ count yield_ count total_cpu_usage_ ms total_cpu_idle_capped_ ms total_scheduler_delay_ ms 0 0 0 1 22,203 7,721 46,142 95,230 0 91 0 1 1 0 22,970 8,111 49,480 102,421 0 106 0 2 2 0 30,502 5,314 49,305 121,554 0 121 0 3 3 0 12,397 9,696 40,543 69,750 0 61 0 4 4 0 22,287 6,337 44,481 103,434 0 86 1 5 5 0 15,887 6,903 39,894 86,495 0 38 1 6 6 0 24,370 6,747 47,111 103,339 0 65 1 7 7 1 25,358 6,399 47,999 109,649 0 65 1 8 8 0 14,900 8,252 40,767 79,162 0 55 1 9 9 48 22,781 7,306 47,003 100,998 0 72 2 10 64 0 21,579 6,928 45,093 96,210 0 58 2 11 65 0 23,295 8,136 48,233 101,061 0 63 2 12 66 0 22,502 6,977 46,290 100,698 0 54 2 13 67 1 13,837 7,318 37,243 76,688 0 56 2 14 68 0 21,533 7,012 45,133 96,726 0 57 3 15 69 0 23,529 6,417 46,516 104,630 0 58 3 16 70 0 17,607 7,427 41,484 85,782 0 44 3 17 71 0 24,409 6,650 46,839 105,316 0 62 3 18 72 0 24,960 7,195 48,150 103,118 0 59 3 19 73 0 16,729 6,931 39,798 86,645 0 47

28. Copyright© WinTechnology Corporation. All Rights Reserved. Linux SQLOS Schedulers 240 Sec 稼働状況 parent_node_id scheduler_id cpu_id preemptive_switches_count context_switches_count idle_switches_count yield_count total_cpu_usage_ms total_cpu_idle_capped_ms total_scheduler_delay_ms 0 0 0 0 19,474 6,835 43,462 94,789 0 923 0 1 1 0 20,942 -3,135 46,247 95,549 0 993 0 2 2 0 20,078 6,885 42,159 91,197 0 947 0 3 3 0 29,345 5,629 48,804 115,854 0 1,279 0 4 4 0 27,999 5,966 48,840 112,233 0 1,220 1 5 5 0 15,620 7,620 40,088 79,975 0 519 1 6 6 0 16,707 7,405 40,920 84,984 0 593 1 7 7 0 26,614 6,036 47,778 110,424 0 921 1 8 8 48 26,909 5,781 47,204 111,040 0 932 1 9 9 0 25,413 6,353 46,634 105,125 0 863 2 10 10 0 11,711 6,848 35,088 73,257 0 477 2 11 11 0 21,675 8,892 45,747 88,522 0 793 2 12 12 0 22,178 6,952 45,621 96,315 0 801 2 13 13 0 28,991 6,043 49,571 111,199 0 1,077 2 14 14 0 20,496 6,734 43,696 95,437 0 738 3 15 15 0 22,142 9,657 50,039 94,136 0 767 3 16 16 0 12,310 7,151 34,838 70,170 0 435 3 17 17 0 29,887 6,316 51,177 114,183 0 1,075 3 18 18 0 21,039 6,972 44,303 95,150 0 753 3 19 19 0 19,053 7,669 42,975 87,492 0 667

29. Copyright© WinTechnology Corporation. All Rights Reserved. SQLOS waitstats 比較 Windows and SQL Server Linux and SQL Server wait_type waiting_tasks_ count wait_ time_ms max_wait_ time_ms signal_wait_ time_ms wait_type waiting_ tasks_Count wait_time_ ms max_wait_ time_ms signal_wait_ time_ms SOS_SCHEDULER_YIELD 595,314 1,434,382 41 1,434,187SOS_SCHEDULER_YIELD 590,051 1,485,767 24 1,485,588 HADR_FILESTREAM_IOMGR_IOCOMPLETION 693 350,859 515 13WRITELOG 132,044 372,787 36 182,053 DIRTY_PAGE_POLL 3,202 350,647 203 16DIRTY_PAGE_POLL 2,862 288,116 109 6 WRITELOG 131,512 316,414 152 173,801HADR_FILESTREAM_IOMGR_IOCOMPLETION 574 287,705 504 48 CXPACKET 20,527 52,478 157 14,251CXPACKET 21,293 58,597 187 15,830 MEMORY_ALLOCATION_EXT 9,599,926 7,633 1 0MEMORY_ALLOCATION_EXT 9,725,974 8,598 4 0 LCK_M_S 1,412 6,102 156 1,582LCK_M_S 1,311 4,886 29 1,459 LCK_M_U 1,508 3,667 84 824PREEMPTIVE_OS_AUTHENTICATIONOPS 4,809 4,784 12 0 PAGELATCH_EX 5,318 3,206 7 2,417PAGEIOLATCH_EX 2,582 3,395 24 140 PAGEIOLATCH_EX 2,365 3,155 167 98LCK_M_U 1,240 2,927 24 907 RESERVED_MEMORY_ALLOCATION_EXT 3,829,782 2,053 0 0PAGELATCH_EX 3,837 2,656 10 2,037 THREADPOOL 201 1,291 20 0RESERVED_MEMORY_ALLOCATION_EXT 4,056,191 2,172 2 0 PAGEIOLATCH_SH 1,016 1,157 20 36ASYNC_NETWORK_IO 874 1,428 12 740 PAGELATCH_SH 428 974 149 242PAGEIOLATCH_SH 1,272 1,201 16 90 ASYNC_NETWORK_IO 865 742 58 223PREEMPTIVE_OS_QUERYREGISTRY 80 400 12 0 PREEMPTIVE_OS_AUTHENTICATIONOPS 4,806 360 10 0PAGELATCH_SH 259 338 12 163 PREEMPTIVE_OS_NETVALIDATEPASSWORDPOLICY 1,600 332 8 0PREEMPTIVE_OS_CRYPTOPS 4,803 333 11 0 CMEMTHREAD 4,740 294 6 283PREEMPTIVE_OS_NETVALIDATEPASSWORDPOLICY 1,601 329 8 0 PREEMPTIVE_OS_CRYPTACQUIRECONTEXT 1,600 201 4 0SESSION_WAIT_STATS_CHILDREN 239 310 12 107 SESSION_WAIT_STATS_CHILDREN 249 186 12 47PREEMPTIVE_OS_CRYPTACQUIRECONTEXT 1,601 286 7 0 PREEMPTIVE_OS_QUERYREGISTRY 102 112 4 0CMEMTHREAD 2,273 268 11 262 PREEMPTIVE_OS_CRYPTOPS 4,800 85 4 0PREEMPTIVE_OS_AUTHORIZATIONOPS 1,602 146 4 0 PAGEIOLATCH_UP 49 75 8 9PREEMPTIVE_OS_NETVALIDATEPASSWORDPOLICYFREE 1,601 101 4 0 EXECSYNC 112 59 11 18PAGEIOLATCH_UP 64 94 12 11 PREEMPTIVE_OS_AUTHORIZATIONOPS 1,601 39 4 0EXECSYNC 76 80 8 16 PREEMPTIVE_OS_NETVALIDATEPASSWORDPOLICYFREE 1,600 32 4 0RESOURCE_SEMAPHORE_MUTEX 30 18 4 18 LCK_M_SCH_S 2 20 17 0LCK_M_X 3 8 6 0 RESOURCE_SEMAPHORE_MUTEX 35 8 4 8LCK_M_SCH_S 1 4 4 3 LATCH_SH 3 4 4 4PREEMPTIVE_XE_CALLBACKEXECUTE 58 0 0 0 LCK_M_SCH_M 1 4 4 3LATCH_EX 13 0 0 0 PREEMPTIVE_OS_DELETESECURITYCONTEXT 1 4 4 0LATCH_SH 9 0 0 0 PREEMPTIVE_XE_CALLBACKEXECUTE 70 0 0 0LCK_M_SCH_M 3 0 0 0 PAGELATCH_UP 2 0 0 0LCK_M_IX 2 0 0 0 PREEMPTIVE_OS_QUERYCONTEXTATTRIBUTES 1 0 0 0PAGELATCH_UP 1 0 0 0 PREEMPTIVE_OS_REVERTTOSELF 1 0 0 0PREEMPTIVE_OS_QUERYCONTEXTATTRIBUTES 1 0 0 0 PREEMPTIVE_OS_WRITEFILE 1 0 0 0PREEMPTIVE_OS_REVERTTOSELF 1 0 0 0 PREEMPTIVE_OS_WRITEFILE 1 0 0 0

30. Copyright© WinTechnology Corporation. All Rights Reserved. Windows & Linux Database File I/O 状況 database_id file_id size_on_disk_bytes num_of_reads num_of_bytes_read io_stall_read_ms io_stall_queued_read_ms num_of_writes num_of_bytes_written io_stall_write_ms io_stall_queued_write_ms io_stall num_of_reads num_of_bytes_read io_stall_read_ms io_stall_queued_read_ms num_of_writes num_of_bytes_written io_stall_write_ms io_stall_queued_write_ms io_stall tempdb data1 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 data2 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 data3 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 data4 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 data5 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 data6 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 data7 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 data8 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 data9 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 data10 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 data11 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 data12 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 data13 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 data14 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 data15 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 data16 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 data17 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 data18 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 data19 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 data20 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 log 1,073,741,824 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 NorthWind data 524,288,000 909 61,120,512 903 0 1,297 18,063,360 463 0 1,366 945 63,766,528 536 0 2,452 33,923,072 1,121 0 1,657 log 1,048,576,000 0 0 0 0 14,977 31,988,736 1,486 0 1,486 0 0 0 0 14,692 64,208,896 3,612 0 3,612 NorthWind2 data 524,288,000 906 61,014,016 885 0 1,296 18,276,352 124 0 1,009 948 63,430,656 678 0 2,465 34,045,952 487 0 1,165 log 1,048,576,000 0 0 0 0 15,272 32,720,896 1,459 0 1,459 0 0 0 0 14,772 64,610,304 3,826 0 3,826 NorthWind3 data 524,288,000 910 61,194,240 913 0 1,273 18,087,936 253 0 1,166 1,002 64,012,288 806 0 2,468 33,841,152 881 0 1,687 log 1,048,576,000 0 0 0 0 15,343 32,790,016 1,153 0 1,153 0 0 0 0 14,460 63,197,184 3,478 0 3,478 NorthWind4 data 524,288,000 907 60,866,560 864 0 1,306 18,178,048 239 0 1,103 994 63,725,568 870 0 2,415 33,677,312 754 0 1,624 log 1,048,576,000 0 0 0 0 14,999 31,906,304 1,265 0 1,265 0 0 0 0 14,508 63,201,280 3,630 0 3,630 NorthWind5 data 524,288,000 906 60,792,832 945 0 1,301 18,227,200 577 0 1,522 951 63,913,984 905 0 2,468 33,693,696 1,105 0 2,010 log 1,048,576,000 0 0 0 0 14,789 32,056,832 1,143 0 1,143 0 0 0 0 14,607 63,348,736 3,640 0 3,640 NorthWind6 data 524,288,000 905 60,940,288 1,014 0 1,308 18,284,544 136 0 1,150 1,002 64,364,544 1,027 0 2,488 34,160,640 1,354 0 2,381 log 1,048,576,000 0 0 0 0 14,950 32,460,288 1,265 0 1,265 0 0 0 0 14,585 63,672,320 3,512 0 3,512 NorthWind7 data 524,288,000 904 60,817,408 1,410 0 1,289 18,268,160 201 0 1,611 950 63,692,800 1,006 0 2,464 34,267,136 1,167 0 2,173 log 1,048,576,000 0 0 0 0 14,855 32,118,784 1,389 0 1,389 0 0 0 0 14,303 62,705,664 3,419 0 3,419 NorthWind8 data 524,288,000 903 60,882,944 1,137 0 1,302 18,202,624 509 0 1,646 952 63,856,640 902 0 2,460 34,119,680 1,170 0 2,072 log 1,048,576,000 0 0 0 0 15,192 31,966,208 1,249 0 1,249 0 0 0 0 14,941 64,876,544 3,742 0 3,742 Windows and SQL Server Linux and SQL Server

31. Copyright© WinTechnology Corporation. All Rights Reserved. 今回の検証で明確になったこと • SQL Server 2017 の快挙 • メモリー利用方法の大幅な改良 • 十分なメモリーがある場合、中間処理等で tempdb を利用しなくなった • Linux 環境の注意事項 • Windows SQL Server SSMS から利用・参照出来ない機能がある • エラーログの参照 • 統合認証が利用できない • Linux SQL Server の再起動 • Windows OS Performance Monitor 相当の監視ツール不足

32. Copyright© WinTechnology Corporation. All Rights Reserved. まとめ • SQL Server on Linux の完成度はとても高い • Windows 環境と同等の H/W OS を含む拡張保守サービスも利用可能 • 今後の Linux 検証予定 • 冗長化機能の確認 • ペースメーカー等によるフェールオーバー機能 • Always On AG による運用 • Windows 環境と同等の監視ツールとチューニング方法の整備 • ETL 動作確認

34. Copyright© WinTechnology Corporation. All Rights Reserved. non-clustered TPC-H@1000GB で性能、価格性能比ともに第一位 HPE, マイクロソフト, レッドハットが、SQL Server 2017 Enterprise Edition 初の結果を公表ベンチマーク結果の要点 • SQL Server 2017 on Red Hat Enterprise Linux が TPC-H@1000GB で以前トップだったSQL Server 2016 の結果を抜いてトップを獲得 • 6% 高い処理性能 • 5% 良い価格性能比 • Microsoft SQL Server 2017 Enterprise Edition 初で唯一の結果 • 2つのIntel® Xeon® E5-2699 v4 プロセッサを搭載した、ほぼ同じ構成のサーバーでの結果成功のためのパートナーシップ $0.64 $0.61 $0.00 $0.50 $1.00 HPE ProLiant DL380 Gen9 w/SQL Server 2016 on Microsoft Windows HPE ProLiant DL380 Gen9 w/SQL Server 2017 on Red Hat Enterprise Linux 678,492 717,101 0 250,000 500,000 750,000 HPE ProLiant DL380 Gen9 w/SQL Server 2016 on Microsoft Windows HPE ProLiant DL380 Gen9 w/SQL Server 2017 on Red Hat Enterprise Linux QphH $ USD/QphH Red Hat Enterprise Linux 7 HPE ProLiant DL380 Gen9 SQL Server 2017 Enterprise Edition より高い処理性能より良い価格性能比

35. Copyright© WinTechnology Corporation. All Rights Reserved. ミッションクリティカル環境におけるLinux利用の悩みを解決 RHELミッションクリティカルサービス日本発 HPEのソリューションお客様のメリット長期サポートとプロアクティブ情報提供 •RHEL EUS* 2年拡張サポート •RHEL AUS** 6年長期サポート重大影響度のセキュリティ問題、緊急優先度の不具合修正を提供 •プロアクティブ情報提供（オプション） • 変更にかかる時間、コストの抑制 • セキュリティ脆弱性や重大な不具合の発生リスクの低減 • システムの長期安定稼働の実現障害対応目標時間の設定 •RHELミッションクリティカルSLAサポート - 24時間以内の解決策（回避策）提示 - 31日以内に恒久対処策の提供 Shift JISの正式サポート •RHEL Shift JIS サポート • 障害からの早期暫定復旧 • システムの安定稼働への早期回復 • 既存環境で蓄積したデータ資産の有効活用 • Unix環境からの移行コストの抑制お客様の悩み悩み１：リリースサイクルとサポート期間悩み２：復旧のめど悩み3: SJISサポート *EUS : Extended Update Support **AUS : Advanced Mission Critical Update Support Red Hat Enterprise Linux（RHEL）をミッションクリティカル環境で利用する際に、システムの長期的な安定稼働を実現するためのサポート

36. Thank you for attending this session 株式会社CSK Winテクノロジ本社東京都新宿区西新宿 6-24-1 西新宿三井ビル 20F 関西事業所大阪府大阪市中央区北浜 1-8-16 大阪証券取引所ビル 13F

[db tech showcase Tokyo 2017] D21: ついに Red Hat Enterprise Linuxで SQL Serverが使える！～Dr. KによるSQL Server 2017 Linux版性能検証速報～ by Winテクノロジ株式会社 熊澤 幸生

Insight Technology, Inc.