Optimization?

Does debugging include optimization (since, theoretically, slow code == bad 
code)? I've been meaning for a while to look into speeding up AmphetaDesk, 
but don't really know what path to take (or whether there is more than one).

I know you can do a bunch of stuff with Dprof (most notably, optimizing the 
first three or so must run routines), but what other optimization tools are 
available to you? How can I find out what's the biggest structure in 
memory? How can I find out what variables are being stored in memory 
(perhaps erroneously)? Etc., etc.

  http://www.ccl4.org/~nick/P/Fast_Enough/
  http://www.panix.com/~comdog/solve_any_perl_problem.pod


-- 
Morbus Iff ( i put the demon back in codemonkey )
Culture: http://www.disobey.com/ and http://www.gamegrene.com/
Buy My Book! http://amazon.com/exec/obidos/ASIN/0596004605/disobeycom
icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus