in reply to Optimizing a CHI-based data throttler

Having done all the rubber-ducking, an epiphany: you do not need to re-calculate the sum of bucket counts every time you try_push(). Instead cache this value and re-calculate it only if a bucket died since last try_push()

bw, bliako

Replies are listed 'Best First'.
Re^2: Optimizing a CHI-based data throttler
by perlancar (Hermit) on Feb 23, 2020 at 05:57 UTC
    Thanks, I'll remember this as one strategy to try. But first I'll do some profiling first.
[reply]

      Preliminary profiling shows that indeed CHI is the bottleneck. 95% of the time is spent outside of Data::Throttler_CHI itself, while CHI::* code itself occupies at least ~73%; the rest of the overhead involves serialization, logging, and so on. Seems like reducing the number of cache item retrievals from CHI would be the primary strategy for speed-up. Or in other words, we need to cache CHI itself, thereby defeating its purpose in the first place :-)

      On the other hand, I manage to speed up Data::Throttler itself significantly simply by replacing Log::Log4perl with Log::ger. The Data::Throttler code logs a lot, so by removing logging statement (e.g. using Log::ger::Plugin::OptAway) we can cut the time into about one third!

[reply]

In Section Seekers of Perl Wisdom