Cache demangling step about blazesym HOT 5 CLOSED

Agreed.
This is what I did for now and it was OK. The docs around demangling options could maybe mention this.

Thanks for considering. Great library, simple APIs!

from blazesym.

I am unsure about this one, to be honest. Yes, there could be some CPU gains to be had, but memory overhead is potentially close to unbounded. I haven't heard of anybody caching demangling results (though that doesn't have to mean much).

Given that the demangling is basically the last step of symbolization, could you built that on top instead? I.e., instruct blazesym to not demangle and then demangle yourself based on a cache. That, or longer term we could perhaps come up with some plug-in caching scheme, where you'd be able to configure the Symbolizer at creation time.

from blazesym.

Proposal for an extra line in the comment over the APIs

    /// The demangling step is not cached (this can have impacts
    /// on performances).

from blazesym.

Good point. Will incorporate your suggestion. Thanks!

from blazesym.

Thanks! Closing for now as the caching step is not essential.

from blazesym.