Smart chunk management
#14
Maybe save the time each chunk was last active. Then the delta (D) between last active time and current time is compared to threshold (T). T should be low (10-30 sec) for chunks not neighboring active chunks and high (120-300 sec) for chunks neighboring active chunk. (it stands to reason chunks neighboring active chunks are more likely to be visited more often.)

When D > T unload, if chunk is "dirty" save and then unload. (so don't distinguish between clean and dirty chunks)

This could ofc be combined with the max ram strategy.
Reply
Thanks given by:


Messages In This Thread
Smart chunk management - by LogicParrot - 04-26-2016, 05:54 PM
RE: Smart chunk management - by LogicParrot - 04-26-2016, 06:06 PM
RE: Smart chunk management - by NiLSPACE - 04-26-2016, 06:12 PM
RE: Smart chunk management - by LogicParrot - 04-26-2016, 06:15 PM
RE: Smart chunk management - by LogicParrot - 04-26-2016, 06:18 PM
RE: Smart chunk management - by NiLSPACE - 04-26-2016, 06:56 PM
Dynamic MAX ram - by LogicParrot - 04-26-2016, 07:29 PM
RE: Smart chunk management - by worktycho - 04-26-2016, 07:47 PM
RE: Smart chunk management - by worktycho - 04-26-2016, 08:35 PM
RE: Smart chunk management - by worktycho - 04-26-2016, 08:37 PM
RE: Smart chunk management - by Schwertspize - 04-26-2016, 09:09 PM
Plugins - by LogicParrot - 04-26-2016, 09:14 PM
RE: Smart chunk management - by worktycho - 04-27-2016, 01:44 AM
RE: Smart chunk management - by Seyaku - 05-26-2016, 12:12 AM



Users browsing this thread: 2 Guest(s)