From: Igor Munkin <imun@tarantool.org> To: Sergey Kaplun <skaplun@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH luajit v2 7/7] tools: introduce a memory profile parser Date: Sun, 27 Dec 2020 01:56:51 +0300 [thread overview] Message-ID: <20201226225651.GI5396@tarantool.org> (raw) In-Reply-To: <03ac70e3bfb9bf7061ad71c1bac50ed3f8e853fc.1608907726.git.skaplun@tarantool.org> Sergey, Thanks for the patch! LGTM, except the several nits below. On 25.12.20, Sergey Kaplun wrote: > This patch adds a parser for binary data dumped via the memory profiler. It is > a set of the following Lua modules: > * utils/bufread.lua: read binary data from a file. > * utils/symtab.lua: symbol table decode functions > * memprof/parse.lua: decode the memory profiler event stream > * memprof/humanize.lua: display decoded data in human readable format > * memprof.lua: Lua script to display data > > There is also a stand-alone bash script <luajit-parse-memprof> that displays > human readable parsed data to a stdout. It calls <memprof.lua> with a > corresponding LUA_PATH. > > Part of tarantool/tarantool#5442 > Part of tarantool/tarantool#5490 > --- > > Changes in v2: > - Add (un)?install sections in Makefile > - Modify bash script correspondingly. > - Change Lua modules layout. > - Adjusted test. Check that errno returns in case of error is added. > - Code clean up. > > Makefile | 39 +++++- > test/misclib-memprof-lapi.test.lua | 135 +++++++++++++++++++++ > tools/luajit-parse-memprof | 9 ++ > tools/memprof.lua | 109 +++++++++++++++++ > tools/memprof/humanize.lua | 45 +++++++ > tools/memprof/parse.lua | 188 +++++++++++++++++++++++++++++ > tools/utils/bufread.lua | 147 ++++++++++++++++++++++ > tools/utils/symtab.lua | 89 ++++++++++++++ > 8 files changed, 757 insertions(+), 4 deletions(-) > create mode 100755 test/misclib-memprof-lapi.test.lua > create mode 100755 tools/luajit-parse-memprof > create mode 100644 tools/memprof.lua > create mode 100644 tools/memprof/humanize.lua > create mode 100644 tools/memprof/parse.lua > create mode 100644 tools/utils/bufread.lua > create mode 100644 tools/utils/symtab.lua > > diff --git a/Makefile b/Makefile > index 4a56917..ba4aa2f 100644 > --- a/Makefile > +++ b/Makefile > @@ -37,6 +37,9 @@ INSTALL_INC= $(DPREFIX)/include/luajit-$(MAJVER).$(MINVER) > > INSTALL_LJLIBD= $(INSTALL_SHARE)/luajit-$(VERSION) > INSTALL_JITLIB= $(INSTALL_LJLIBD)/jit > +INSTALL_UTILSLIB= $(INSTALL_LJLIBD)/utils > +INSTALL_MEMPROFLIB= $(INSTALL_LJLIBD)/memprof Minor: It's better to use $(INSALL_TOOLSLIB) here, isn't it? > +INSTALL_TOOLSLIB= $(INSTALL_LJLIBD) > INSTALL_LMODD= $(INSTALL_SHARE)/lua > INSTALL_LMOD= $(INSTALL_LMODD)/$(ABIVER) > INSTALL_CMODD= $(INSTALL_LIB)/lua <snipped> > diff --git a/test/misclib-memprof-lapi.test.lua b/test/misclib-memprof-lapi.test.lua > new file mode 100755 > index 0000000..e02c6fa > --- /dev/null > +++ b/test/misclib-memprof-lapi.test.lua > @@ -0,0 +1,135 @@ <snipped> > +local function check_alloc_report(alloc, line, function_line, nevents) > + assert(string.format("@%s:%d", arg[0], function_line) == alloc[line].name) > + assert(alloc[line].num == nevents, ("got=%d, ecpected=%d"):format( Typo: s/ecpected/expected/. > + alloc[line].num, > + nevents > + )) > + return true > +end <snipped> > diff --git a/tools/luajit-parse-memprof b/tools/luajit-parse-memprof > new file mode 100755 > index 0000000..c814301 > --- /dev/null > +++ b/tools/luajit-parse-memprof > @@ -0,0 +1,9 @@ > +#!/bin/bash > +# > +# Launcher for memprof parser. > + > +# This two variables are replaced on installing. > +TOOL_DIR=$(dirname `readlink -f $0`) > +LUAJIT_BIN=$TOOL_DIR/../src/luajit > + > +LUA_PATH="$TOOL_DIR/?.lua;;" $LUAJIT_BIN $TOOL_DIR/memprof.lua $@ > diff --git a/tools/memprof.lua b/tools/memprof.lua > new file mode 100644 > index 0000000..7476757 > --- /dev/null > +++ b/tools/memprof.lua > @@ -0,0 +1,109 @@ <snipped> > +local bufread = require "utils.bufread" > +local memprof = require "memprof.parse" > +local symtab = require "utils.symtab" > +local view = require "memprof.humanize" Typo: Still mess with whitespace. > + <snipped> > +local reader = bufread.new(inputfile) > +local symbols = symtab.parse(reader) > +local events = memprof.parse(reader, symbols) Typo: Still mess with whitespace. > + <snipped> > diff --git a/tools/utils/symtab.lua b/tools/utils/symtab.lua > new file mode 100644 > index 0000000..f3e5e31 > --- /dev/null > +++ b/tools/utils/symtab.lua > @@ -0,0 +1,89 @@ > +-- Parser of LuaJIT's symtab binary stream. > +-- The format spec can be found in <src/lj_symtab.h>. I see no such file. I guess you mean <src/lj_memprof.h>. > +-- <snipped> > -- > 2.28.0 > -- Best regards, IM
next prev parent reply other threads:[~2020-12-26 22:56 UTC|newest] Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-25 15:26 [Tarantool-patches] [PATCH luajit v2 0/7] LuaJIT memory profiler Sergey Kaplun 2020-12-25 15:26 ` [Tarantool-patches] [PATCH luajit v2 1/7] utils: introduce leb128 reader and writer Sergey Kaplun 2020-12-25 21:42 ` Igor Munkin 2020-12-26 9:32 ` Sergey Kaplun 2020-12-26 13:57 ` Sergey Kaplun 2020-12-26 18:47 ` Sergey Ostanevich 2020-12-25 15:26 ` [Tarantool-patches] [PATCH luajit v2 2/7] core: introduce write buffer module Sergey Kaplun 2020-12-26 14:22 ` Igor Munkin 2020-12-26 15:26 ` Sergey Kaplun 2020-12-26 19:03 ` Sergey Ostanevich 2020-12-26 19:37 ` Sergey Kaplun 2020-12-28 1:43 ` Sergey Kaplun 2020-12-25 15:26 ` [Tarantool-patches] [PATCH luajit v2 3/7] vm: introduce VM states for Lua and fast functions Sergey Kaplun 2020-12-26 19:07 ` Sergey Ostanevich 2020-12-27 23:48 ` Igor Munkin 2020-12-28 3:54 ` Sergey Kaplun 2020-12-25 15:26 ` [Tarantool-patches] [PATCH luajit v2 4/7] core: introduce new mem_L field Sergey Kaplun 2020-12-26 19:12 ` Sergey Ostanevich 2020-12-26 19:42 ` Sergey Kaplun 2020-12-27 13:09 ` Igor Munkin 2020-12-27 17:44 ` Sergey Kaplun 2020-12-25 15:26 ` [Tarantool-patches] [PATCH luajit v2 5/7] core: introduce memory profiler Sergey Kaplun 2020-12-27 10:58 ` Sergey Ostanevich 2020-12-27 11:54 ` Sergey Kaplun 2020-12-27 13:27 ` Sergey Ostanevich 2020-12-27 16:44 ` Igor Munkin 2020-12-27 21:47 ` Sergey Kaplun 2020-12-25 15:26 ` [Tarantool-patches] [PATCH luajit v2 6/7] misc: add Lua API for " Sergey Kaplun 2020-12-27 11:54 ` Sergey Ostanevich 2020-12-27 13:42 ` Sergey Kaplun 2020-12-27 15:37 ` Sergey Ostanevich 2020-12-27 18:58 ` Igor Munkin 2020-12-28 0:14 ` Sergey Kaplun 2020-12-25 15:26 ` [Tarantool-patches] [PATCH luajit v2 7/7] tools: introduce a memory profile parser Sergey Kaplun 2020-12-26 22:56 ` Igor Munkin [this message] 2020-12-27 7:16 ` Sergey Kaplun 2020-12-28 5:30 ` Sergey Kaplun 2020-12-28 5:33 ` Igor Munkin 2020-12-28 6:28 ` Sergey Kaplun 2020-12-28 6:31 ` Igor Munkin 2020-12-27 13:24 ` Sergey Ostanevich 2020-12-27 16:02 ` Sergey Kaplun 2020-12-27 21:55 ` Sergey Ostanevich 2020-12-28 2:05 ` [Tarantool-patches] [PATCH luajit v3 2/2] misc: add Lua API for memory profiler Sergey Kaplun 2020-12-28 2:49 ` Igor Munkin 2020-12-28 5:19 ` Sergey Kaplun 2020-12-28 2:06 ` [Tarantool-patches] [PATCH luajit v3 1/2] core: introduce " Sergey Kaplun 2020-12-28 3:59 ` Igor Munkin 2020-12-28 4:05 ` [Tarantool-patches] [PATCH luajit v3 3/7] vm: introduce VM states for Lua and fast functions Sergey Kaplun 2020-12-28 5:14 ` Igor Munkin 2020-12-28 6:01 ` [Tarantool-patches] [PATCH luajit v2 0/7] LuaJIT memory profiler Alexander V. Tikhonov 2020-12-28 8:15 ` Igor Munkin
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20201226225651.GI5396@tarantool.org \ --to=imun@tarantool.org \ --cc=skaplun@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH luajit v2 7/7] tools: introduce a memory profile parser' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox