| title | Disable Lightweight Pooling | Microsoft Docs | |
|---|---|---|
| ms.custom | ||
| ms.date | 08/09/2016 | |
| ms.prod | sql | |
| ms.prod_service | database-engine | |
| ms.reviewer | ||
| ms.technology | security | |
| ms.topic | conceptual | |
| helpviewer_keywords |
|
|
| ms.assetid | 481bb43d-6fe5-497c-9096-971fb6bf733b | |
| author | VanMSFT | |
| ms.author | vanto |
[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md] This rule checks that lightweight pooling is disabled on the server. Setting lightweightpooling to 1 causes [!INCLUDEssNoVersion] to switch to fiber mode scheduling. Fiber mode is intended for certain situations in which the context switching of the UMS workers is the important bottleneck in performance. Because this is rare, fiber mode seldom improves performance or scalability on the typical system.
The lightweightpooling option should only be enabled after thorough testing, after all other performance tuning opportunities are evaluated, and when context switching is a known issue in your environment.
We recommend that you do not use fiber mode scheduling for routine operation because it can decrease performance by preventing the regular benefits of context switching, and because some components of [!INCLUDEssNoVersion] that use Thread Local Storage (TLS) or thread-owned objects, such as mutexes (a kind of Win32 kernel object), cannot function correctly in fiber mode
To remove lightweight pooling, execute the following statement, and then restart the [!INCLUDEssDEnoversion].
sp_configure 'show advanced options', 1;
GO
sp_configure 'lightweight pooling', 0;
GO
RECONFIGURE;
GO lightweight pooling Server Configuration Option
Monitor and Enforce Best Practices by Using Policy-Based Management