Debug options for IRHydra (deoptimizations tracing) #7122
Comments
|
Can i hope to see IRHydra2 support in nearest releases? AFAIK v8 is now upgraded to acceptable version. |
--print-opt-code only works when V8 is compiled with ENABLE_DISASSEMBLER. That flag is disabled in release builds unless v8_enable_disassembler=1 is set. Is it worth it to enable it by default? It will make the binary a few hundred kB bigger and add a few seconds to the build. |
I use node to write high-speed modules. Last example is https://github.com/nodeca/pako , that is just 1.3 time slower than native C code. Problem with such modules is lack of easily accessible tools. IMHO, good instruments will motivate developpers to do interesting things. I'll be fine with ANY one-click solution, that will not require manually edit configs and rebuild node froum src. Special official dev build will be ok, for example. |
IRHydra2 can be used with current master. You only need the build option if |
IMHO, viewing assembly src is useful, to better understand if optimized code still contains unboxing calls or not. This also helps to locate problem places, because IRHydra2 not always can find exact string number in js, that caused deoptimization. |
@trevnorris @bnoordhuis ... any further thoughts on this one? |
I know the disassembler was enabled in the io.js build, but I forget if it was done in Node.js. |
Ok, so the question then becomes: should we enable it in joyent/node master or v0.12 going forward or simply pick it up in the converged stream? |
Don't believe so. Will close this then! |
It would be nice to have more options for deoptimizations debug: http://mrale.ph/irhydra/2/
--print-opt-code
Is it possible to enable those by default? If not, is it possible to have ready dev binaries, that can be installed easy via
nvm
and so on. Building dev configuration manually is not convenient.The text was updated successfully, but these errors were encountered: