Is there any way to limit the frequency of map updates? I'm using the Windows dedicated server at the moment, and it seems to check for map updates every 60 seconds, and then hits hard disk and memory to do this.
Disclaimer: Googling the issue and searching these forums mostly leads to either people not knowing any solution, or threads here with a user named "�omano" gaslighting people telling them that this is either not an issue, or things like "OS do actually check surely way more thing that you apparently imagine, every second" which is false, and insane. �omano, if you read this, do not bother posting in this thread. I do not want your "help". You are a registered user, and I don't want you crapping on my thread making it look like you resolved my ignorance.
With that out of the way, Tripwire, this is silly. You really don't need to check for update to the entire map list every 60 seconds -- if checking all maps takes 60 seconds or more, this just constantly has a task going that adds to CPU wait, checking the same maps which, frankly, are barely updated nowadays. I think it would be perfectly reasonable to check for updates to all maps upon server start (possibly with a flag to disable this in cases of large amounts of maps), and to check a map's up-to-date status before loading it. The idea that all maps need to be updated every minute regardless of which maps you might be actually playing on to keep a consistent state (never mind your not checking stock maps update status) is overkill. It might make sense in the case of a linux server via colocation with high concurrency where resources are far more available, but as a side thing for my friends and I on one of my home computers, it's incredibly wasteful and inconvenient.
While I think changing this default behavior would be most desirable, I also understand it's probably a pain, so even just a flag to change the update frequency (or turn it off) would be incredibly helpful.
P.S. Tripwire, use utf8mb4/utf8mb4_unicode_ci for your database character set/collation, and serve pages with meta tags indicating the character set is utf8, with PHP using utf8 to resolve the � issue in usernames/posts, etc.
Disclaimer: Googling the issue and searching these forums mostly leads to either people not knowing any solution, or threads here with a user named "�omano" gaslighting people telling them that this is either not an issue, or things like "OS do actually check surely way more thing that you apparently imagine, every second" which is false, and insane. �omano, if you read this, do not bother posting in this thread. I do not want your "help". You are a registered user, and I don't want you crapping on my thread making it look like you resolved my ignorance.
With that out of the way, Tripwire, this is silly. You really don't need to check for update to the entire map list every 60 seconds -- if checking all maps takes 60 seconds or more, this just constantly has a task going that adds to CPU wait, checking the same maps which, frankly, are barely updated nowadays. I think it would be perfectly reasonable to check for updates to all maps upon server start (possibly with a flag to disable this in cases of large amounts of maps), and to check a map's up-to-date status before loading it. The idea that all maps need to be updated every minute regardless of which maps you might be actually playing on to keep a consistent state (never mind your not checking stock maps update status) is overkill. It might make sense in the case of a linux server via colocation with high concurrency where resources are far more available, but as a side thing for my friends and I on one of my home computers, it's incredibly wasteful and inconvenient.
While I think changing this default behavior would be most desirable, I also understand it's probably a pain, so even just a flag to change the update frequency (or turn it off) would be incredibly helpful.
P.S. Tripwire, use utf8mb4/utf8mb4_unicode_ci for your database character set/collation, and serve pages with meta tags indicating the character set is utf8, with PHP using utf8 to resolve the � issue in usernames/posts, etc.