I came across the same problem profiling a project I was working on in IE. IE6 is particularly bad since the scripting engine seems to be the slowest (sadly at over 50% of the market - it's the most important browser).
The best thing I could come up with was a timing profiler - which in the end did identify some serious bottlenecks in IE (lots of pngfixes turned out to be one problem of mine). It wrote a module that could time normal start/stops, events, functions and anonymous functions without having to change much code. Here's the link and few examples on the page: http://remysharp.com/2007/04/20/performance-profiling-javascript/ Some of my colleagues are trying out MS Visual Studio for the scripting tools - but I'm not particularly hopeful. Hope that helps (a bit!). Remy. On Jul 23, 5:28 pm, Gordon <[EMAIL PROTECTED]> wrote: > Does anyone know of an IE equivilent to Firebug that I can use to > profile code run times in a similar manner? I have been working hard > over the last few weeks optimizing some jQuery driven code, and after > doing all the obvious stuff (cacheing selectors, reducing loops, etc) > I have been trying more tricky optimization tricks, such as cacheing > the DOM attributes of elements I manipulate a lot so I don't have to > use .attr and .css getters for conditional statements. > > I have been using the Firebug code profiler to test how my code's > performance is improving, and unscientific throw-a-lot-of-elements-at- > it-and-see-how-it-affects-performance tests in Opera and Safari. > While most of the things I've tried have had a positive impact (albeit > a rather small one in a few cases), IE seems to be gaining much less > performance than the other browsers. > > I'd like to be able to profile the code I'm working on in IE the same > way I can in FireBug, but have so far failed to find a decent free > open source profiler. If anyone has a pointer to something I can use > I'd appreciate it. Alternativly if you have any tips regarding things > known to be slow specifically in Explorer that don't have a > significant negitive impact in the other browsers I'd also find that > helpful as I can look for them in my code.
