Skip to content

Latest commit

 

History

History
55 lines (46 loc) · 3.83 KB

File metadata and controls

55 lines (46 loc) · 3.83 KB
title lightweight pooling Server Configuration Option | Microsoft Docs
ms.custom
ms.date 03/02/2017
ms.prod sql
ms.prod_service database-engine
ms.service
ms.component configure-windows
ms.reviewer
ms.suite sql
ms.technology
database-engine
ms.tgt_pltfrm
ms.topic article
helpviewer_keywords
default lightweight pooling
decreasing overhead
lightweight pooling option
system overhead [SQL Server]
performance [SQL Server], lightweight pooling
context switching [SQL Server], lightweight pooling option
excessive context switching [SQL Server]
reducing overhead
overhead [SQL Server]
ms.assetid 2dc11b61-d065-4126-8e00-acf40390f9fb
caps.latest.revision 31
author MikeRayMSFT
ms.author mikeray
manager craigg
ms.workload Inactive

lightweight pooling Server Configuration Option

[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md]

Use the lightweight pooling option to provide a means of reducing the system overhead associated with the excessive context switching sometimes seen in symmetric multiprocessing (SMP) environments. When excessive context switching is present, lightweight pooling can provide better throughput by performing the context switching inline, thus helping to reduce user/kernel ring transitions.

Fiber mode is intended for certain situations in which the context switching of the UMS workers are the critical bottleneck in performance. Because this is rare, fiber mode rarely enhances performance or scalability on the typical system. Improved context switching in [!INCLUDEmsCoName] [!INCLUDEwinxpsvr] has also reduced the need for fiber mode. We do not recommend that you use fiber mode scheduling for routine operation. This is because it can decrease performance by inhibiting 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 type of Win32 kernel object), cannot function correctly in fiber mode.

Setting lightweight pooling to 1 causes [!INCLUDEssNoVersion] to switch to fiber mode scheduling. The default value for this option is 0.

The lightweight pooling option is an advanced option. If you are using the sp_configure system stored procedure to change the setting, you can change lightweight pooling only when show advanced options is set to 1. The setting takes effect after the server is restarted.

Note

Lightweight pooling is not supported for [!INCLUDEmsCoName] Windows 2000 and [!INCLUDEmsCoName] Windows XP. [!INCLUDEwinxpsvr] provides full support for lightweight pooling.

Note

Common language runtime (CLR) execution is not supported under lightweight pooling. Disable one of two options: "clr enabled" or "lightweight pooling". Features that rely upon CLR and that do not work properly in fiber mode include the hierarchy data type, replication, and Policy-Based Management.

See Also

clr enabled Server Configuration Option
Server Configuration Options (SQL Server)
sp_configure (Transact-SQL)
clr enabled Server Configuration Option