in reply to Last hurdle.. Merge hash refs or change data dump?

Did you even measure how much time you lose with Hash::Merge?

I don't expect it to be a big performance hit, or to even be measurable compared to normal startup time and noise.

  • Comment on Re: Last hurdle.. Merge hash refs or change data dump?

Replies are listed 'Best First'.
Re^2: Last hurdle.. Merge hash refs or change data dump?
by cosmicperl (Chaplain) on Apr 16, 2008 at 13:26 UTC
    Problem is in my scenario the config files are read in on some click tracking that needs to be able to handle hundreds or thousands (or even more) of clicks per second. So even the slightest performance drop will scale up to having a big effect.
      But these micro-optimzations are the wrong solution.

      Better use something like mod_perl or fastcgi where you have a persistent program in memory, so you don't have to deal with module loading and other startup costs for every hit.

        I'll be implementing a FastCGI version and I've been helping the FastCGI team out with their site. But for the time being I've been working hard on all the micro optimizations and it's been paying off.