Oracle 5.0 Reference Manual page 519

Option Sets Variable
Variable Name
Variable Scope
Dynamic Variable
This variable is unused.
• [499]
table_type
Variable Name
Variable Scope
Dynamic Variable
Deprecated
This variable is a synonym for
is the preferred name;
•
thread_cache_size
Command-Line Format
Option-File Format
Option Sets Variable
Variable Name
Variable Scope
Dynamic Variable
How many threads the server should cache for reuse. When a client disconnects, the client's threads
are put in the cache if there are fewer than
for threads are satisfied by reusing threads taken from the cache if possible, and only when the
cache is empty is a new thread created. This variable can be increased to improve performance
if you have a lot of new connections. Normally, this does not provide a notable performance
improvement if you have a good thread implementation. However, if your server sees hundreds
of connections per second you should normally set
so that most new connections use cached threads. By examining the difference between the
[524]
Connections
the thread cache is. For details, see
•
thread_concurrency
Command-Line Format
Option-File Format
Option Sets Variable
Variable Name
Variable Scope
Server System Variables
Yes,
table_lock_wait_timeout
table_lock_wait_timeout
Global
Yes
Permitted Values
Type
numeric
Default
50
Range
1 .. 1073741824
table_type
Global, Session
Yes
5.2.5, by
storage_engine
Permitted Values
Type
enumeration
storage_engine
[499] is deprecated and is removed in MySQL 5.5.
table_type
[499]
--thread_cache_size=#
thread_cache_size
Yes,
thread_cache_size
thread_cache_size
Global
Yes
thread_cache_size
and
Threads_created
Section 5.1.6, "Server Status
[499]
--thread_concurrency=#
thread_concurrency
Yes,
thread_concurrency
thread_concurrency
Global
499
[498]
[497]. In MySQL 5.0,
[499]
[499]
thread_cache_size
[534] status variables, you can see how efficient
Variables".
[499]
[497]
storage_engine
threads there. Requests
[499] high enough