Just checking to be sure, but did you run nytprofhtml? The files it generates contain a wealth of information, all hyperlinked for easy perusal.
If you generated the flame graph then you can also readily see which call stacks are taking all the time. It's one way to see if the AUTOLOAD and DESTROY stacks are due to one code path, or are split across many.
There should also be a set of links immediately below the "spent" lines you are quoting which will allow you to trace which ones are taking all the time or are being called the most.
In reply to Re: Win32::OLE Excel temporary objects destruction
by swl
in thread Win32::OLE Excel temporary objects destruction
by ndts
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |