On Thu, May 8, 2008 at 12:19 AM, David Wilson <[EMAIL PROTECTED]> wrote: > On that note, John suggested sharking in his first response, and your > response to him was "I know what's happening, so I don't think Shark > or Instruments can help any." I would very strongly suggest that this > response is very wrong- a shark session would have very rapidly shown > both the strlen call and the appenddata calls to be extreme hotspots > in your code, which might have pointed you to the problem.
To put this more generally: if you think you know what's slow in your code and you haven't measured it, then you're most likely wrong. In this case, of course, the poster *didn't* know what was slow. The first step in optimization is knowing you have a problem by measuring how long things take. (Noticing that some operation takes nearly a minute to run when it shouldn't is sufficient.) The next step is to profile to find out what parts of the code are sucking up all of the time. Once you've done these two, only then are you prepared to start actually making things go faster. Mike _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
