How Node.js applications will benefit from replacing V8 in JXcore
oguzbastemur.blogspot.com
How Node.js applications will benefit from replacing V8 in JXcore
1–10 of 24 posts
Re: How Node.js applications will benefit from replacing V8 in JXcore
#2They should clearly state that this is a private fork (as in, not open source).
Re: How Node.js applications will benefit from replacing V8 in JXcore
#3They should clearly state that this is a private fork (as in, not open source).
Please read the last paragraph ( we are committed to 'entirely' open source it, right after the engine switch )
Re: How Node.js applications will benefit from replacing V8 in JXcore
#4How exactly does JXCore manage to beat years worth of optimisation engineering by Google? I'm skeptical, especially since I can imagine an engineering tradeoff between performance and stability. Maybe V8 is slower because they fixed crash bugs caused by overoptimistic code generation. What assurances does anyone have that their slower but working V8 code won't be fast and broken in a new engine?
Re: How Node.js applications will benefit from replacing V8 in JXcore
#5They should clearly state that this is a private fork (as in, not open source).
Please read the last paragraph ( we are committed to 'entirely' open source it, right after the engine switch )
I love what you are doing, so don't get me wrong but it's just a declaration of intent and not binding. Also, not being open source can make people question where actually the speed difference comes from. Did you trade stability with speed? A shortcut for a common operation? Who knows!
Re: How Node.js applications will benefit from replacing V8 in JXcore
#6What are you doing computing heavy stuff in JS for?
Re: How Node.js applications will benefit from replacing V8 in JXcore
#7I thought bigger means faster for Octane scores. Isn't this showing that their engine has about 75% of the performance of V8?
Re: How Node.js applications will benefit from replacing V8 in JXcore
#8Earlier quoted context omitted.
Please read the last paragraph ( we are committed to 'entirely' open source it, right after the engine switch )
I love what you are doing, so don't get me wrong but it's just a declaration of intent and not binding. Also, not being open source can make people question where actually the speed difference comes from. Did you trade stability with speed? A shortcut for a common operation? Who knows!
Yet this is just a declaration for now, we do not have any intention to keep it closed source. There is no need to trade stability with speed since most of the 'current' performance difference with JXcore comes from less amount of JS native switches and better memory management. Very soon we will be open sourcing it! Thanks
Re: How Node.js applications will benefit from replacing V8 in JXcore
#9I thought bigger means faster for Octane scores. Isn't this showing that their engine has about 75% of the performance of V8?
Yes, bigger is better in Octane scores. And by god we are optimizing the hell out of Octane these days, so I doubt the premise of this post.
Re: How Node.js applications will benefit from replacing V8 in JXcore
#10How exactly does JXCore manage to beat years worth of optimisation engineering by Google? I'm skeptical, especially since I can imagine an engineering tradeoff between performance and stability. Maybe V8 is slower because they fixed crash bugs caused by overoptimistic code generation. What assurances does anyone have that their slower but working V8 code won't be fast and broken in a new engine?
It doesn't. The benchmark clearly shows that V8 is faster than JXCore, because lower scores are worse.