• Subject: Re: Work In Progress: About Lua Structures
• From: Spar <developspartv@...>
• Date: Fri, 13 Nov 2020 03:00:29 +0300

Hi. The link just go down, here is working link for sure: https://github.com/GitSparTV/lua-infographics/tree/main/lua-benchmark/

Sharing my knowledge.
I was learning LuaJIT bytecode some time ago, and discovered that for 64bit versions the TValue struct is actually shared between 2 TValues objects.
As assume this is done for pointer/RAM optimizations.
However, for the same reason LuaJIT had to make 2 versions of bytecode: regular (32 bit) and with FR2 (Frame Size 2). 64-bit bytecode is not compatible with 32-bit executable and the opposite.
Devs said they might add compatibility between them later, but this did not happen yet.

He also discussed it here: https://github.com/LuaJIT/LuaJIT/issues/209

I don't have enough knowledge and experience in this field to say if that's a benefit, so I just shared some information I know.

On Fri, Nov 13, 2020 at 1:38 AM Ranier Vilela <ranier.vf@gmail.com> wrote:
Hi,

Work In Progress: About Lua structures
Sizeofs 64 bits (msvc 2019 64 bits):
Instruction: 4
TValue: 16
TString: 32
LClosure: 40
Proto: 128

I'm studying the structures of Lua, and one caught my attention: struct Proto

I think it's breaking the cache line in two.
After running the factorial test (https://github.com/GitSparTV/lua-infographics/blob/main/lua-benchmark/benchmark.lua)

An information caught my attention:
returning: / * trap already set * /
0.04s cl = clLvalue (s2v (cy-> func));
0.13s k = cl-> p-> k;
0.01s pc = cy-> u.l.savedpc;
0.01s if (trap) {

A simple move is taking an average of 0.15s (0.13s to 0.15s).
0.13s k = cl->p->k;

Wouldn't Lua benefit from dividing struct Proto in two?
Would it pay off?

regards,
Ranier Vilela