- Joined
- Jan 6, 2003
- Messages
- 1,139
So we've looked at the differences between the Steam forum and BladeForum.
As we thought, mysql configuration appears to be, at least initially, very similar. For example the Steam forum uses the following changes to the my.cnf (mysql configuration) file:
set-variable = thread_stack=128K
set-variable = max_connections=400
set-variable = key_buffer=128M
set-variable = max_allowed_packet=1M
set-variable = table_cache=128
set-variable = sort_buffer=1M
set-variable = record_buffer=1M
set-variable = myisam_sort_buffer_size=64M
set-variable = max_connect_errors=10000
This is almost exactly how Jacob has BladeForums mysql set up.
The biggest difference was that the Steam forums have enough memory to fit the entire working set of the database into memory.
So, as a first step, we are going to increase the memory in the database server from 1 GB to 4 GB. This is a relatively brute force approach that has the attractive characteristics of 1) being relatively cheap, 2) if it doesn't solve the performance problems it will tell us a lot more about where the real problems lie, and 3) more memory in a server never hurt anybody.
Kevin, do you know what kind of memory is in the servers? If not, then either what motherboard is installed, or from whom did you buy the servers?
Jacob said he'd be happy to install the memory for us, and, in general, has been very responsive and helpful.
As we thought, mysql configuration appears to be, at least initially, very similar. For example the Steam forum uses the following changes to the my.cnf (mysql configuration) file:
set-variable = thread_stack=128K
set-variable = max_connections=400
set-variable = key_buffer=128M
set-variable = max_allowed_packet=1M
set-variable = table_cache=128
set-variable = sort_buffer=1M
set-variable = record_buffer=1M
set-variable = myisam_sort_buffer_size=64M
set-variable = max_connect_errors=10000
This is almost exactly how Jacob has BladeForums mysql set up.
The biggest difference was that the Steam forums have enough memory to fit the entire working set of the database into memory.
So, as a first step, we are going to increase the memory in the database server from 1 GB to 4 GB. This is a relatively brute force approach that has the attractive characteristics of 1) being relatively cheap, 2) if it doesn't solve the performance problems it will tell us a lot more about where the real problems lie, and 3) more memory in a server never hurt anybody.
Kevin, do you know what kind of memory is in the servers? If not, then either what motherboard is installed, or from whom did you buy the servers?
Jacob said he'd be happy to install the memory for us, and, in general, has been very responsive and helpful.