dongfuye
dongfuye
@cabol It is strange that the original untouched test cases failed.
implement this proposal https://github.com/cabol/nebulex/issues/184
> @dongfuye apologies for the lateness on this one, but actually I've been working on something which will make this new strategy feature more seamless I'd say. Will get back...
Looking forward to Nebulex v3, and I'll update this feature according to V3's architecture. I would suggest to use this feature as the default local cache GC strategy, since configuration...
Thank you for your response. It is glad to discuss such an important strategy on this great project with you. The above proposal has not included the strategy to check...
> the strategy consists of having a fixed timeout (let's call it gc_cleanup_timeout) that will check whether the size and/or memory have exceeded the limit but only for the current/newest...
I have not considered keeping the old configurations before, so I will take some time to design it. Maybe I will reply to this tomorrow.
The configuration proposal: The new version of configuration for Nebulex should be as simple as possible. The user only need to set only one option, for example: `generation_max_size`. Following are...
The internal behavior is exactly the same. My suggestion of this new option is based on following reasons: - For the new strategy, using the name `: generation_max_time` may be...
OK, I agree to rename `:generation_max_time` to `:generation_start_timeout` I am currently on vacation until next weekend, and then I'll implement this new strategy and make a PR.