Griffinator
Programmer
Hi all,
I'm a relative newbie to mySQL, so please bear with me. The problem I am having is as follows:
I am currently in the process of developing an app which uses mySQL version 3.23.53-max-nt and myODBC version 2.50 as the backend, and Visual Basic 6 using ADO as the front end. I have installed mySQL on 3 different systems for testing purposes, and it seems to be working flawlessly on 2 out of the 3. The steps I took to install it were exactly the same on all 3 systems.
However, on the third system I have been running out of Virtual Memory, and I have no idea why. It is an XP system running at 900 Mhz with 640 MB of RAM, and its Pagefile space is set to max out at 1000 MB. I have noticed over several occasions that Windows will warn me that it has run out of Pagefile space, and when I check the task manager my Pagefile usage shows in the neighborhood of 900+ MB used. I have mySQL set to start as a service, so it starts automatically when Windows boots.
The puzzling part about my problem is that this will happen without even running any queries through mySQL to my databases. I have tested it where I simply started the machine and left it run for roughly 8 hours, and when I checked it the Pagefile space had nearly ran out. If I shut down the mysqld-nt.exe service, my Pagefile usage will drop to normal levels (around 200 MB). Even more puzzling is it is not consistent, in other words, it doesn't do this all of the time so I cannot establish a pattern as to what might be causing it.
My question is this: Is there something I am missing in the configuration of mySQL or possibly the myODBC driver, or is it system specific? For comparitive purposes, the second system is a 1.8 Ghz running XP with 256 MB of RAM, and the third system is an 800 Mhz running XP with 96 MB of RAM (I know, it seems silly, but there is a reason.....). Again, both of these systems seemingly run fine, however I did initially run out of Pagefile space on the 800 Mhz system, but increasing the max Pagefile size seems to have alleviated the problem.
I have included the relevant parts of the my.ini file for you to look at (if this is even where my problem might reside):
[mysqld]
basedir=C:/mysql
innodb_data_home_dir=
innodb_data_file_path = ibdata1:10M:autoextend
set-variable = innodb_buffer_pool_size=320M
set-variable = innodb_additional_mem_pool_size=10M
set-variable = innodb_log_file_size=65M
set-variable = innodb_log_buffer_size=8M
innodb_flush_log_at_trx_commit=1
Any help that you could give me would be greatly appreciated, as I am more or less against a brick wall on this one.
Thanks in advance,
Griffinator
I'm a relative newbie to mySQL, so please bear with me. The problem I am having is as follows:
I am currently in the process of developing an app which uses mySQL version 3.23.53-max-nt and myODBC version 2.50 as the backend, and Visual Basic 6 using ADO as the front end. I have installed mySQL on 3 different systems for testing purposes, and it seems to be working flawlessly on 2 out of the 3. The steps I took to install it were exactly the same on all 3 systems.
However, on the third system I have been running out of Virtual Memory, and I have no idea why. It is an XP system running at 900 Mhz with 640 MB of RAM, and its Pagefile space is set to max out at 1000 MB. I have noticed over several occasions that Windows will warn me that it has run out of Pagefile space, and when I check the task manager my Pagefile usage shows in the neighborhood of 900+ MB used. I have mySQL set to start as a service, so it starts automatically when Windows boots.
The puzzling part about my problem is that this will happen without even running any queries through mySQL to my databases. I have tested it where I simply started the machine and left it run for roughly 8 hours, and when I checked it the Pagefile space had nearly ran out. If I shut down the mysqld-nt.exe service, my Pagefile usage will drop to normal levels (around 200 MB). Even more puzzling is it is not consistent, in other words, it doesn't do this all of the time so I cannot establish a pattern as to what might be causing it.
My question is this: Is there something I am missing in the configuration of mySQL or possibly the myODBC driver, or is it system specific? For comparitive purposes, the second system is a 1.8 Ghz running XP with 256 MB of RAM, and the third system is an 800 Mhz running XP with 96 MB of RAM (I know, it seems silly, but there is a reason.....). Again, both of these systems seemingly run fine, however I did initially run out of Pagefile space on the 800 Mhz system, but increasing the max Pagefile size seems to have alleviated the problem.
I have included the relevant parts of the my.ini file for you to look at (if this is even where my problem might reside):
[mysqld]
basedir=C:/mysql
innodb_data_home_dir=
innodb_data_file_path = ibdata1:10M:autoextend
set-variable = innodb_buffer_pool_size=320M
set-variable = innodb_additional_mem_pool_size=10M
set-variable = innodb_log_file_size=65M
set-variable = innodb_log_buffer_size=8M
innodb_flush_log_at_trx_commit=1
Any help that you could give me would be greatly appreciated, as I am more or less against a brick wall on this one.
Thanks in advance,
Griffinator