[feature request] backport lua 5.4 generational GC
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.4k
- Forks
- 252
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 3
Description
ATT.
I'm developing using OpenResty and have put heavy logic on lua(with relatively large in-memory data and lot of string manipulation, and a lot of functions), and I noticed that those permanent GC object also slows down GC.
If we can mannually specify object as permanent it may also be sufficient for my case.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The request concerns LuaJIT garbage collection for OpenResty workloads and proposes backporting Lua 5.4 generational GC or manually marking permanent objects. No files, tests, or entry points are named; begin by locating the garbage collector implementation and comparing the requested Lua 5.4 behavior. Done requires an agreed design and validated GC behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, lua
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100