Tarantool development patches archive
 help / color / mirror / Atom feed
From: Sergey Bronnikov via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Maxim Kokryashkin <m.kokryashkin@tarantool.org>
Cc: Maxim Kokryashkin <max.kokryashkin@gmail.com>,
	tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit 2/2] profilers: purge generation mechanism
Date: Fri, 6 Oct 2023 17:45:22 +0300	[thread overview]
Message-ID: <8db5ce8b-2ced-44cc-81b2-83058fd5cda8@tarantool.org> (raw)
In-Reply-To: <9c1f5176-6bcc-4a35-bf80-40ad3e2d6074@tarantool.org>


On 10/6/23 17:43, Sergey Bronnikov via Tarantool-patches wrote:
> Hi, Max
>
> On 9/18/23 12:18, Maxim Kokryashkin wrote:
>> Hi, Sergey!
>> Thanks for the comments!
>> Here is the new message:
>> =======
>> 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
>
>
> Seems you forgot force-push to the branch.
>
Please disregard.

  reply	other threads:[~2023-10-06 14:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-28 15:23 [Tarantool-patches] [PATCH luajit 0/2] profilers: purge generations 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 [this message]
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 ` [Tarantool-patches] [PATCH luajit 0/2] profilers: purge generations Igor Munkin via Tarantool-patches

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=8db5ce8b-2ced-44cc-81b2-83058fd5cda8@tarantool.org \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=m.kokryashkin@tarantool.org \
    --cc=max.kokryashkin@gmail.com \
    --cc=sergeyb@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH luajit 2/2] profilers: purge generation mechanism' \
    /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