I won't be able to look at the Shark traces until later, but both of the functions you list are Quicktime internals. What version of QT are you using?
On 3/17/06, B. Bogart ben@ekran.org wrote:
Hi Chris,
Here are a couple links:
This one was the profile done while the video is running fine: http://www.ekran.org/ben/research/While-PD-runs-fine@start.mshark
This is the one once PD has been running for a while (20-30min): http://www.ekran.org/ben/research/Pd-is-now-slogging.mshark
Looks like while things are looking ok 25% CPU goes into "DecodeBlocks" which looks like the decompression process. When things go bad it looks like "mentorGetNextFrame" takes up 45% so that looks like the problem. Sorry I don't have the debugging symbols in this gem binary, but I hope the profiles can still help.
Thanks for the tips Chris, shark is indeed pretty sharp... :)
.b.
On Fri, March 17, 2006 11:33 am, chris clepper said:
Use this URL instead http://developer.apple.com/tools/sharkoptimize.html
On 3/17/06, chris clepper cgc@humboldtblvd.com wrote:
I just realized that there is no need for me to test your patch. You can install the Apple CHUD tools and run Shark yourself. All of the directions are on this page:
http://developer.apple.com/tools/performance/optimizingwithsystemtrace.html
Save the session and post it online somewhere and one of us will have a look.
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev