Live data from Hacker News

LuaJIT 2.1 Profiler released

permalink.gmane.org

1–10 of 21 posts

Re: LuaJIT 2.1 Profiler released

#3
The 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 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

#4
Slightly 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

#5
post #3

The 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…

python

Re: LuaJIT 2.1 Profiler released

#6
post #3

The 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…

V8?

Re: LuaJIT 2.1 Profiler released

#7
post #4

Slightly 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.

Either use NNTP, or http://gmane.org/export.php

Re: LuaJIT 2.1 Profiler released

#8
post #3

The 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…

Smalltalk? Lisp?

Re: LuaJIT 2.1 Profiler released

#9
LuaJIT is a work of great beauty and efficiency. I've been working on a commercial product for small ARM boards where rapid prototyping has been essential because of ever changing requirements but the speed of the finished code is also paramount. LuaJIT has made this project an absolute pleasure. It wraps C libraries cleanly, it runs within 5-10% of native code speed on the ARM (I checked because I didn't believe it at first) and it's 100% compatible with all the Lua 5.1 supporting libraries I need. This new profiler will be a great addition to the toolbox along with ZeroBrane Studio's debugger which I just discovered this week and which also rocks.

Mike Pall needs several Jolt Awards.

Re: LuaJIT 2.1 Profiler released

#10
post #3

The 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…

Sampling for CPU performance, instrumentation for control flow analysis and memory allocation.

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.

Post reply on HN