On Thu, Jan 21, 2010 at 9:49 PM, Tres Seaver <tsea...@palladion.com> wrote: > IIUC, optimizing your application using standard (non-JITed) profiling > tools would still be a win for the app when run under the JIT, because > your are going to be trimming code / using better algorithms, which will > tend to provide "orthagonal" speedups to anything the JIT does. The > worst case would be that you hand-optimze the code to the point that the > JIT can't help any longer, kind of like writing libc syscalls in > assembler rather than C.
You'd hope. I don't think it's quite that simple, though. The problem is code might have completely different hotspots with the JIT than without it. The worst case in this scenario would be that some code takes 1 second to run function A and 30 seconds to run function B without the JIT, but 30 seconds to run function A and 1 second to run function B with the JIT. The profiler's telling you to put all your effort into fixing function A, but you won't see any significant performance gains no matter how often you change it. Generally, that's not going to be the case. But the broader point--that you've no longer got an especially good idea of what's taking time to run in your program--is still very valid. -- Chris _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
