Quote:
Originally Posted by Verstehen
I rebuilt the cache to just the last few weeks and it doesn't make any difference. Python using 50+% of CPU while 4-tabling, with a very simple HUD and import time set to every 40 seconds. Any other ideas?
Are you seeing a difference when playing with the pulse time?
How long do the graphs take to generate?
Quote:
Should I try rebuilding index? Or maybe changing some preferences? I have already changed "stat_range" to T from A in preferences so that it doesn't try to use the whole DB.
Making sure Hero is set to T should minimise the size of the query.
Reindex is a good idea, but i'm not sure how long it will take (or if it will even complete) on a db that size.
Configuring MySQL may help things too.
Are you technically competent? i'd like to run a few things from the command line and see if we can't identify the issue. I suspect we can improve the index on the HudCache to perform better with large dbs.
Quote:
One thing I've noticed is that "cachesessions" and "faststoreHUDcache" are turned off in my import preferences, do I need to change that?
cachesessions being off should be fine. faststoreHUDcache is now legacy and doesn't actually do anything.
Quote:
here's a screenshot of prefs if this helps at all:
Thanks so much guys.
EDIT: BTW I am using the 0.25 from the .deb installation.
Could you switch off callFbdbHud and 4 table and tell me if the CPU usage is still that high?
Sorrow.