LuaJIT 2.1 Profiler released
permalink.gmane.org
LuaJIT 2.1 Profiler released
1–10 of 21 posts
Re: LuaJIT 2.1 Profiler released
#2Re: LuaJIT 2.1 Profiler released
#3As you might have noticed, I had to change my plans compared to the original approach presented in June. The main problem with the instrumenting profiler was finding high-precision and high-speed timing sources for all platforms. (...) The necessary pipeline flushes shadowed the actual timings up to the point where the measurements were less accurate than with a sampling profiler! Other platforms offered only inaccurate timing sources or none that are accessible from user mode. And to top it off, the instrumentation added considerable overhead. (...) I had to scrap that work and decided to go with a sampling profiler.
And I don't know any other scripting language with a built-in sampling profiler. Does anybody?
Re: LuaJIT 2.1 Profiler released
#4Re: LuaJIT 2.1 Profiler released
#5The most interesting conclusions of Mike Pall reflect my experiences: sampling profilers are often much more usable in practice than instrumentation: As you might have noticed, I had to change my plans compared to the original approach presented in June. The main problem with the instrumenting profiler was finding high-precision and high-speed timing sources for all platforms. (...) The necessary pipeline flushes sha…
Re: LuaJIT 2.1 Profiler released
#6The most interesting conclusions of Mike Pall reflect my experiences: sampling profilers are often much more usable in practice than instrumentation: As you might have noticed, I had to change my plans compared to the original approach presented in June. The main problem with the instrumenting profiler was finding high-precision and high-speed timing sources for all platforms. (...) The necessary pipeline flushes sha…
Re: LuaJIT 2.1 Profiler released
#7Slightly off-topic, but does anyone know how I can download the complete mailing list archive data (of luajit)? Many of Mike's posts are very informative and useful, and I'd like to be able to search/read them easily, offline.
Re: LuaJIT 2.1 Profiler released
#8The most interesting conclusions of Mike Pall reflect my experiences: sampling profilers are often much more usable in practice than instrumentation: As you might have noticed, I had to change my plans compared to the original approach presented in June. The main problem with the instrumenting profiler was finding high-precision and high-speed timing sources for all platforms. (...) The necessary pipeline flushes sha…
Re: LuaJIT 2.1 Profiler released
#9Mike Pall needs several Jolt Awards.
Re: LuaJIT 2.1 Profiler released
#10The most interesting conclusions of Mike Pall reflect my experiences: sampling profilers are often much more usable in practice than instrumentation: As you might have noticed, I had to change my plans compared to the original approach presented in June. The main problem with the instrumenting profiler was finding high-precision and high-speed timing sources for all platforms. (...) The necessary pipeline flushes sha…
The distortion effect of measurement is higher with instrumentation, and is the chief reason I prefer sampling when trying to find performance problems.
But finding CPU performance issues is far from the only reason for using a profiler.