Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Large overhead from expires times when highly populated #8
Commonly seeing 20-40k timer instances due to a timer being created for each cache entry. Outside of the CPU overhead that this might incur (I don't know the node internals, other than that there is some sort of linked list going on), this does create a lot of memory overhead.
In one particular dump seeing 30megs+ of retained data for these timers, domains, protects, etc that are all associated with each timer instance.
Under our use pattern these timers commonly trigger at very similar times and it seems like with some smart bucketing and a prune setInterval or similar much of this overhead could be dramatically reduced.