Swancutt: Sorry, *4* gb of JSON
Navarrete: Danblack: the web server in question has 16 GB of RAM, would 2 GB be more than enough do you think?
Rothenberg: Mr_Midnight: depends on your datasize however that would be a good minimium setting at rought estimate
Rutheford: There should never be a need to schedule regularly a shutdown of mysql.
Bisom: Danblack: I don’t necessarily trust the MS installer to have done the best job installing mysql especially since when I try to do an upgrade the mysql 5.5 installer doesn’t want to upgrade the current mysql 5.1 install
Kamai: I am probably going to end up rebuilding the server at some point if your suggestions don’t help out the load times
Keiter: Is that the standard troubleshooting approach for windows users?
Preyor: It does sound like a typical windows admin solution. understanding is a better one.
Meints: In my situation where I didn’t build out the server and I don’t trust a 3rd party installer to properly install mysql yes that would be my solution. if I had built the server and knew what was done to begin with along with any customizations then I wouldn’t be so quick to rebuild
Pieratt: Also if this was hosting more than a single wordpress website on it I wouldn’t be so quick to rebuild but I can backup the wordpress website and restore it to a new server fairly quickly.
Blaze: Guys, is it possible to increase the phpmyadmin upload limit in shared hosting ?
Keiter: Arunpyasi: ask #phpmyadmin
Ganer: Danblack: I just changed the buffer pool size, and then rebooted the server with no other changes I tend to only make one change at a time when doing work on a server in case a change breaks something the startup time of mysql appears to be unaffected and there is no improper shutdown of the mysql database this time. http://pastebin.com/yH6jZmqp
Cubie: Mr_Midnight: i’d keep it like that anyway. there are logs of benefits of a decent innodb_buffer_pool size. ***uming all the tables are innnodb however.
Iadarola: Danblack: any idea if WordPress uses innodb? That’s all that is in this mysql install
Keiter: Mr_Midnight: you can query the information_schema.tables
Obermeyer: Hmm. might have just found the issue. was trying some more google searching and found an obscure post from 5 years ago online that said to try a different temp file path. so I made that change to the my.ini and killed the service and restarted it and everything seems to have started up properly. doing a reboot shortly
Keiter: Mr_Midnight: why do you keep rebooting?
Calaycay: Keiter: because I am also installing windows updates on this server as it hasn’t been patched in about 9 months
Schardein: Each round of updates needs a reboot so I am trying to just keep pace
Feiertag: Omg it works. Thank you both Keiter and danblack for your input and patience with me and my lack of mysql knowledge
Ashraf: So what exactly ‘worked’?
Honza: Danblack: I changed the temp directory from C:WindowsTemp to D:mysqltemp
Wassenaar: And now mysql starts up as I would expect it to. about 10 seconds after the windows login screen appears
Ciccarello: The windows temp folder was so full of crap which I am cleaning up now it was causing major issues for mysql apparently
Sefcheck: Mr_Midnight: ok good. sounds like a filesystem limitation but good to know it can be worked oround with a client temp foler
Rains: And 10 seconds sounds like a much saner startup time. hopefully its a clean startup and than an unclean start is a similar time.
Kerne: Last couple reboots have been clean start/stops . now next weekend I can focus on trying to get this install of mysql 5.1 to upgrade to 5.5
Keiter: Danblack: we could try to add 10k files to the tmpdir on linux and see if it slows down a clean start
Steckman: Also if you two have more up to date versions I don’t know if they would have the same issue.
Stravinski: Anyway thanks again time for me to crash for the night