Hey just wanted to mention that this convergence issue is not critical, so if we might have some time to look at startup time that would be cool. That pr has the latest prism hooked up but starts up weirdly slow.
Hey @Charles Nutter ! Really happy to see you around here :smile:
For Redline, I need to fix those 3 items: https://github.com/bytecodealliance/endive/issues 201/202/203 and we can re-evaluate, I'll try to prioritize but I'm a bit swamped (a bit worst than usual ...)
I added some comments on all of those. Let me know if you have questions about how JRuby handles thread interrupts for Ruby.
Here's the startup time difference for JRuby legacy parser vs native prism vs WASM prism btw
[] jruby $ time jruby --dev -e 1
jruby --dev -e 1 0.71s user 0.11s system 165% cpu 0.493 total
[] jruby $ time jruby -Xparser.prism --dev -e 1
jruby -Xparser.prism --dev -e 1 0.65s user 0.10s system 168% cpu 0.444 total
[] jruby $ time jruby -Xparser.prism.wasm --dev -e 1
jruby -Xparser.prism.wasm --dev -e 1 1.55s user 0.18s system 176% cpu 0.979 total
Hey I see that 202 and 203 have been resolved. Not sure what your criteria is for releasing but I'd be happy with what you have right now :-)
I'll try a snapshot build with my JRuby branch and see how startup looks now
New startup times looking much better! Still a bit slower than starting up with legacy parser but it's almost there. About 70 .rb files get parsed at boot.
numbers: https://gist.github.com/headius/f1adee542d7267dc124c91784fb52725
Prism native (not through Endive) is similar to legacy parser startup or a little bit faster, for comparison
Thanks a lot for the doublecheck @Charles Nutter !
Numbers look very promising :-)
Quick question, do you have any time constraint?
I can release anytime, but I was thinking about end of the month (October 2026) to be able to tight things a little more.
Last updated: Oct 11 2026 at 04:10 UTC