Tarantool development patches archive
 help / color / mirror / Atom feed
From: Igor Munkin via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Maxim Kokryashkin <max.kokryashkin@gmail.com>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit 0/2] profilers: purge generations
Date: Thu, 23 Nov 2023 06:32:54 +0000	[thread overview]
Message-ID: <ZV7yFh6ajrybZHbI@tarantool.org> (raw)
In-Reply-To: <cover.1693236068.git.m.kokryashkin@tarantool.org>

Max,

I've checked the patchset into all long-term branches in
tarantool/luajit and bumped a new version in master, release/2.11 and
release/2.10.

On 28.08.23, Maxim Kokryashkin via Tarantool-patches wrote:
> This series refactors memprof's binary data parser, so it
> doesn't require generations now. Since both profilers don't
> need generations now, that mechanism is purged to improve
> memory footprint.
> 
> Branch: https://github.com/tarantool/luajit/tree/fckxorg/memprof-parser-refactoring
> PR: https://github.com/tarantool/tarantool/pull/9051
> 
> Maxim Kokryashkin (2):
>   memprof: refactor symbol resolution
>   profilers: purge generation mechanism
> 
>  .../gh-5813-resolving-of-c-symbols.test.lua   |  7 +-
>  .../misclib-memprof-lapi.test.lua             | 73 +++++--------------
>  tools/memprof/humanize.lua                    | 16 ++--
>  tools/memprof/parse.lua                       |  4 +-
>  tools/memprof/process.lua                     |  8 +-
>  tools/sysprof/parse.lua                       |  9 +--
>  tools/utils/avl.lua                           |  4 +-
>  tools/utils/symtab.lua                        | 33 +++------
>  8 files changed, 50 insertions(+), 104 deletions(-)
> 
> -- 
> 2.41.0
> 

-- 
Best regards,
IM

      parent reply	other threads:[~2023-11-23  6:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-28 15:23 Maxim Kokryashkin via Tarantool-patches
2023-08-28 15:23 ` [Tarantool-patches] [PATCH luajit 1/2] memprof: refactor symbol resolution Maxim Kokryashkin via Tarantool-patches
2023-09-03 10:14   ` Sergey Kaplun via Tarantool-patches
2023-09-04  5:44     ` Maxim Kokryashkin via Tarantool-patches
2023-09-05 11:47   ` Sergey Bronnikov via Tarantool-patches
2023-09-08 11:04     ` Maxim Kokryashkin via Tarantool-patches
2023-10-06 14:52       ` Sergey Bronnikov via Tarantool-patches
2023-08-28 15:23 ` [Tarantool-patches] [PATCH luajit 2/2] profilers: purge generation mechanism Maxim Kokryashkin via Tarantool-patches
2023-09-03 10:21   ` Sergey Kaplun via Tarantool-patches
2023-09-04  5:47     ` Maxim Kokryashkin via Tarantool-patches
2023-09-05 11:53   ` Sergey Bronnikov via Tarantool-patches
2023-09-12 10:26     ` Maxim Kokryashkin via Tarantool-patches
2023-09-14  9:47       ` Sergey Bronnikov via Tarantool-patches
2023-09-18  9:18         ` Maxim Kokryashkin via Tarantool-patches
2023-10-06 14:43           ` Sergey Bronnikov via Tarantool-patches
2023-10-06 14:45             ` Sergey Bronnikov via Tarantool-patches
2023-10-06 14:40       ` Sergey Bronnikov via Tarantool-patches
2023-10-06 14:52       ` Sergey Bronnikov via Tarantool-patches
2023-11-13 18:48       ` Igor Munkin via Tarantool-patches
2023-11-23  6:32 ` Igor Munkin via Tarantool-patches [this message]

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=ZV7yFh6ajrybZHbI@tarantool.org \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=imun@tarantool.org \
    --cc=max.kokryashkin@gmail.com \
    --subject='Re: [Tarantool-patches] [PATCH luajit 0/2] profilers: purge generations' \
    /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