![]() It caused lots of problems trying to use innodb_file_per_table, because the mysqld process couldn't work with that many open file descriptors efficiently. So it was about 160,000+ tables per instance. In our case, we had about 1500 schemas per MySQL instance, and a little over 100 tables per schema. I was working on a system with the same problem as yours. ibd file is not scanned before the server starts accepting connections.Īny help to guide me in the right direction would be much appreciated. Question: Is my logic reasonable and could this innodb_file_per_table be the reason for the slow startup? Or is there some other config variable that I can change so that each. So to my understanding, innodb_file_per_table = ON is more beneficial when there are single tables that can get pretty large which is not the case for my server. ![]() One thing to note is that in general, every database size is pretty small and even with 7000 databases, the total size of the data is about 60gb only. Would changing innodb_file_per_table = OFF and then altering each table to get rid of the. In my configuration, I observed that innodb_file_per_table = ON (which is the default for MySQL 5.7 I believe) and so I think that at startup it is scanning every. Is there any way to reduce the startup time? The server works fine when it is running but the startup time can get pretty long, almost 20-30 mins after a clean shutdown of the MySQL service and 1+ hours after a restart of the Windows VM. I understand this is not the recommended set up for MySQL but some business requirements have necessitated this multi-tenant db structure and I cannot change that unfortunately. I have MySQL 5.7.24 running on a Windows VM.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |