|
Ran
|
Jobs
1
|
Files
89
|
Run time
10s
|
Badge
README BADGES
|
push
github
profilers: purge generation mechanism Since both of the profiler parsers are now processing the events in a stream-like fashion, the generation mechanism is excessive and can be purged. This results in a significant memory consumption drop, especially for the AVL-tree part. Consider this script: | jit.off() | misc.sysprof.start{mode = 'C', interval=10} | for i = 1, 1e7 do tostring(i) end | misc.sysprof.stop() After executing it with LuaJIT, you can parse it like this: | $ time -v luajit-parse-sysprof sysprof.bin So, before the patch: | Maximum resident set size (kbytes): 224928 And after the patch: | Maximum resident set size (kbytes): 32780 That is the 85% reduction in memory consumption. Follows up tarantool/tarantool#8700 Reviewed-by: Sergey Kaplun <skaplun@tarantool.org> Reviewed-by: Sergey Bronnikov <sergeyb@tarantool.org> Signed-off-by: Igor Munkin <imun@tarantool.org> (cherry picked from commit 090117d83)
5335 of 5958 branches covered (0.0%)
Branch coverage included in aggregate %.
20441 of 23231 relevant lines covered (87.99%)
692289.42 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 6854723657.1 | 0 |
88.31 |
GitHub Action Run |