in reply to Re^3: How to put a fat program on a (memory) weight-loss diet?
in thread How to put a fat program on a (memory) weight-loss diet? [SOLVED]

  1. Moose objects are hash based objects, that won't change anything
  2. Depending on the actual classes (how many methods it has and how many attributes it has) it would be WAY more savings then 1/10th the size :)
  3. It may or may not run any quicker, Moose is pretty fast at runtime and vanilla Moose accessors typically benchmark pretty close to typical hand coded accessors (sure you can micro-optimize, but you loose readability/maintainability)

The Moose "bloat" is coming from the metaclass instances, it is hard to reduce this because of two factors.

  1. That is what gives Moose all it's power
  2. Perl does not return memory to the OS, even if you DESTROY all your objects

-stvn
  • Comment on Re^4: How to put a fat program on a (memory) weight-loss diet?

In Section Seekers of Perl Wisdom