18:02:09drmeisterOnce we find it, and kill it, and dance on its grave - fastgf will live up to its name.
18:03:40drmeisterI'm working on getting profiling working better
18:03:43beachSo, are you saying that the slowness is still in calling generic functions?
18:04:12beachOr, are you not so sure about that, even?
18:04:40drmeisterThe problem has been that the backtraces gathered from tracing have been unmanageable.
18:05:01drmeisterThey are full of return addresses with no symbol information (due to the JIT) and C++ frames.
18:06:53drmeisterI'm capturing JIT events now and generating a symbol table and now I'm writing a symbolicator program that will text swap addresses of the form 0xYYY to symbol names. symbolicator -s symbol-table-file <file-full-of-0xYY >file-with-symbol-names
18:07:35drmeisterThen we can build flame graphs from tracing info.
18:07:56drmeisterI did your single step through instructions to look at the fastgf call sequence - it's very short now.