Table of Contents
Advertisement
On Windows NT, the default native pool is always being used and Enterprise
Server uses fibers (user-scheduled threads) for initial request processing. Using
custom additional pools on Windows NT introduces no additional overhead.
The directives are:
•
NativePoolStackSize
•
NativePoolMaxThreads
•
NativePoolMinThreads
•
NativePoolQueueSize
NativePoolStackSize
Determines the stack size of each thread in the native (kernel) thread pool.
Default
0
NativePoolMaxThreads
Determines the maximum number of threads in the native (kernel) thread pool.
Enterprise Server
Default
128
NativePoolMinThreads
Determines the minimum number of threads in the native (kernel) thread pool.
Default
1
NativePoolQueueSize
Determines the number of threads that can wait in the queue for the thread pool. If
all threads in the pool are busy, then the next request-handling thread that needs to
use a thread in the native pool must wait in the queue. If the queue is full, the next
request-handling thread that tries to get in the queue is rejected, with the result that
it returns a busy response to the client. It is then free to handle another incoming
request instead of being tied up waiting in the queue.
Default
0
Chapter 7
Syntax and Use of magnus.conf
Native Thread Pools
269
Advertisement
Table of Contents
