-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optimize DB for Influx timer? #66
Comments
All queries are threaded. I doubt it's any plugins' fault. You sure you didn't load a workshop map and it had to update? |
i dont use workshop map. i use last version of timer from git. |
my base size 60 mb and load so long and i dont use influx_zones_checkpoint. db load on server start up - 60-120 seconds. i think simple ranks make this load so long. |
Are you using SQLite? |
mysql db |
@rsgua Do you have already optimized the database server on its own? On my old HLG Surf servers i also had 40mb database but no problems with db load. I can suggest that you optimize your DB Server at first then the plugin. |
You need a good mysql hoster that it. |
db load so long now! on last version! older version load more fast! cRUSHER-HLG i dont know mysql that say this! I know more than you! |
I host it on my own database rootserver. Its the same settings like on old HLG-Surf servers |
@rsgua Try recompiling the plugins using the database (core/checkpoint/etc.) with all CREATE TABLE ... queries removed. They should all exist in */db.sp . |
Hello i have some problem with time with load db.
Can you make sql request for create indexes in your timer?
Some maps load a 6 minutes:(
I disable influx_zones_checkpoint and db load on few seconds!
The text was updated successfully, but these errors were encountered: