I sort of missed this thread. Before Cannon/w0dk4 come with any form of their joint-server idea we plan to do a few steps that could help:
- I'll try to bump up the overclock back to 4,2-4,4GHz where it was stable before. We reduced it to 4,0 in the times when it was crashing 10-20 times a day. But the issue was elsewhere. This could gain us additional 5-10% performance
- we'll try to re-enable the multithreading patch (forcing flhook to run on another core). But if this raises the number of crashes it will be disabled again. Again 5-10%.
- I'll significantly reduce the number of daily backups. They are now done 8 times a day, but once a day should do as the database doesn't get corrupt so often any more.
So for now:
- no more reducing NPC spawn, it's already been reduced
- no high latency/packetloss auto kicking (before we test it further), I am not sure if the current flhook feature is 100% reliable
- leave poor aussies alone...;)
Let's see what happens, and maybe try to plan larger battles outside the peak times?