On 04/02/13 06:25, exarkun@twistedmatrix.com wrote:
On 05:39 pm, john.m.camara@gmail.com wrote:
I have been noticing a pattern where many who are writing Python code to run on PyPy are relying more and more on using the jitviewer to help them write faster code. Unfortunately, many of them who do so don't look at improving the design of their code as a way to improve the speed at which it will run under PyPy but instead start writing obscure Python code that happens to run faster under PyPy. [...] Do others here share this same opinion and should some warning be added to the jitviewer?
What makes you think people will even read this warning, let alone prioritize < it over their immediate desire to make their program run faster?
(Not that I am objecting to adding the warning, but I think you might be fooling yourself if you think it will have any impact)
I think that if the coder is actually using some sort of profiling tool, any sort of profiling tool, that makes them 1000 times more likely to read and pay attention to the warning than the average coder who optimizes code by guessing. Other than that observation, I don't have an opinion on whether jitviewer should come with a warning. (Oh, and another thing... I'm assuming you mean for jitviewer to print the warning as part of it's normal output.) -- Steven