lj_str_new and lj_tab hashkey CPU 100%
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.4k
- Forks
- 252
- Avg merge
- 7d 11h
- Merged PRs (30d)
- 3
Description
lj_str_new CPU 100% only in one core
large number of strings longer than 128 in the mlcache cache. biz logic necessity
Flame Graph:
Perf Data:
Using host libthread_db library "/lib64/libthread_db.so.1".
0x00007f9086d786f9 in lj_str_new (L=0x53f113f0, str=0x40926ae0 "{"event":"mlcache:invalidations:_cache","source":"mlcache","data":"AUTH_OUTER_VER_KEY_X4eTEiMr-jLHD5z0VzzRPFLPOtKLwgLKQXq-TAFyOjl8vv5u2Cn2uQPthlHjlqhr11y4ZioD6L","pid":12861}e\":\"bearer\",\"exp"..., lenx=180) at lj_str.c:198
198 lj_str.c:
https://github.com/openresty/luajit2/blob/v2.1-agentzh/src/lj_str.c
Related issue:
https://github.com/openresty/luajit2/issues/60
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
Start with src/lj_str.c at lj_str_new, especially line 198, and review the supplied flame graph and perf data. Compare the behavior with related issue #60; the issue does not define a specific fix or completion test, so confirm the intended resolution with maintainers before proceeding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100