Bug #8543 Incorrect thread_cache_size parameter writen to my.ini
Submitted: 16 Feb 2005 13:16 Modified: 17 Apr 2008 18:41
Reporter: David Newcomb (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Installing Severity:S3 (Non-critical)
Version:4.1.10 OS:Windows (Win2000)
Assigned to: Iggy Galarza CPU Architecture:Any
Tags: qc

[16 Feb 2005 13:16] David Newcomb
Description:
After installing and configuring the essentials version of MySQL. The my.ini file containts:
--snip--
# How many threads we should keep in a cache for reuse. When a client
# disconnects, the client's threads are put in the cache if there aren't
# more than thread_cache_size threads from before.  This greatly reduces
# the amount of thread creations needed if you have a lot of new
# connections. (Normally this doesn't give a notable performance
# improvement if you have a good thread implementation.)
thread_cache=20
--snip--

How to repeat:
Double click icon.
Select 'Complete' install
Select 'Skip Sign-Up'

Check 'Configure the MySQL Server now', then next
Select 'Detailed Configuration', then next
Select 'Server Machine', then next
Select 'Multifunctional Database', then next
Select 'Manual Settings' set to 100, then next
Check 'Enable TCP/IP Networking', port = 3306, then next
Select 'Best Support For Multilingualism', then next
Check 'Install As Windows Service' (MySQL/Launch automatically)
Check 'Include Bin Directory in Windows PATH', then next
Uncheck 'Modify Security Settings', then next
Click Execute.

Suggested fix:
thread_cache_size=20
[16 Feb 2005 13:49] David Newcomb
Just noticed, even though I have selected:

  'Multifunctional Database' (MyISAM) it still sets :
     default-storage-engine=INNODB

Also setting 'Manual Setting - approximate number of concurrent connections' to 100 dose not add anything to my.ini but dose set
     max_connections=160
[21 Feb 2005 17:48] Alfredo Kojima
The thread_cache_size has been fixed. 
The 'approximate number of concurrent connections' is used as a parameter to calculate the value of some options, together with other values such as memory size, amount of memory used for other things etc. So, there is no additional option that is added to my.ini. Instead max_connections will be derived from the concurrent connections number (a certain slack will be given to it).

As for the default storage engine problem, we will check it.
Thanks for reporting the bug.
[14 Dec 2005 23:53] Jim Winstead
Fixing category.
[23 Dec 2007 6:11] Jeffrey Pugh
Note that the bug mentioned in the Subject is fixed; the remaining bug is that default storage engine is set as InnoDB incorrectly in one case.
[11 Jan 2008 18:01] Iggy Galarza
The Configuration Wizard uses a template to generate the server configuration file.  The Database Usage dialog sets one of the following option strings:

Multifunctional Database:        MIXED
Transactional Database Only:     INNODB
Non-Transactional Database Only: MYISAM

When these options are processed through the default template (my-template.ini) the result is:

Multifunctional Database:
default-storage-engine=InnoDB
_myisam_pct=50

Transactional Database Only:
default-storage-engine=InnoDB
_myisam_pct=5

Non-Transactional Database Only:
default-storage-engine=MyISAM
_myisam_pct=100
skip-innodb

Note: The _myisam_pct value is used to calculate the percentage of resources dedicated to MyISAM.  The remaining resources are allocated to InnoDB.

Since there can only be one default storage engine, this is correct.
[17 Apr 2008 18:41] Paul DuBois
No changelog entry possible. Bug report contains no information about which release trees the fixes were pushed to.  "bk changes" output has no information, either.