Questions about luaj

[mentorj]

Hi,
I am interested in this project , because of the OpenResty heavily used inside one of my projects. I wonder if using a Java interpreter rather than luajit may bring performance improvements, robustness & flexibility.
So before starting hard work I would like to have a few answers:

• did you consider using Java native threads coming with Java 21 to carry Lua co-routines, the mapping sounds perfect and it may be safer & simpler than storing them into WeakReferences, collecting them, waking up threads to check if they may be collected...
• do you have benchmarks regarding performance of the interpreter compared to Luajit ?

Thanks for your help
regards
Jerome

[taoguan]

Thank you Jerome.
It is a good idea to use java vitural thread in lua co-routines, I will take it into plan.
As your second question, I think it is better to use Luajit in C project and it will bring higher performance than luaj.

[mentorj]

Hi taoguan, thanks for the reply... One of the trivial pros for the luaj (but there may be many cons) is the metrics provided by the JVM. For the moment as far as I know, we don't have in production metrics for the Lua related stuff.Is the code cached, how efficient is this cache ? Can we raise the cache size ? Best regards Jerome

…

On Mon, Nov 4, 2024 at 11:56 AM taoguan ***@***.***> wrote: Thank you Jerome. It is a good idea to use java vitural thread in lua co-routines, I will take it into plan. As your second question, I think it is better to use Luajit in C project and it will bring higher performance than luaj. — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEWT7KIDNIEPMENJ3KAMKTZ65HFVAVCNFSM6AAAAABOPO7FCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJUGQYDCMBXG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- J.MOLIERE - Mentor/J

[taoguan]

Hi Jerome,
there is no cache for the code.
It will parse the code and get the new value everytime when we call like this : LuaValue result = globals.loadfile(luaFileName), even though the same lua file.

[mentorj]

Thanks for clarification

…

On Mon, Nov 4, 2024 at 3:32 PM taoguan ***@***.***> wrote: Hi Jerome, there is no cache for the code. It will parse the code and get the new value everytime when we call like this : LuaValue result = globals.loadfile(luaFileName), even though the same lua file. — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEWT7KZ53SP5ONOXMIV43TZ66ARBAVCNFSM6AAAAABOPO7FCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJUHA3TENZWGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- J.MOLIERE - Mentor/J