From: Konstantin Osipov <kostja.osipov@gmail.com>
To: Alexander Turenko <alexander.turenko@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [small] Revert "Free all slabs on region reset"
Date: Thu, 30 Jan 2020 00:41:22 +0300 [thread overview]
Message-ID: <20200129214122.GB31458@atlas> (raw)
In-Reply-To: <4e734e626aba336b27ec85790747c657d29c0338.1580284383.git.alexander.turenko@tarantool.org>
* Alexander Turenko <alexander.turenko@tarantool.org> [20/01/29 11:11]:
> This reverts commit 67d7ab44ab09df3356929e3692a03321b31f3ebb.
>
> The goal of the reverted commit was to fix flaky fails of tarantool
> tests that checks amount of memory used by a fiber:
>
> | fiber.info()[fiber.self().id()].memory.used
>
> It also attempts to overcome the situation when a fiber holds some
> amount of memory, which is not used in any way. The high limit of such
> memory is controlled by a threshold in fiber_gc() tarantool's function
> (128 KiB at the moment):
The commit by Georgy was doing the right thing, it just had a bug
in it. I saw Georgy posted a fix for his commit - but I haven't
seen it on the list.
Why revert this commit rather than fix it? It should be pretty
strightforward to fix, no?
The fix is to avoid iterating over all the free slabs when we
failed to find the right slab size several times, and just get a
new slab at once. I'd even say that Georgy's commit was entirely
correct, it just didn't account for the "land mine" it is setting
for alloc case.
Thoughts?
--
Konstantin Osipov, Moscow, Russia
next prev parent reply other threads:[~2020-01-29 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 8:06 Alexander Turenko
2020-01-29 9:59 ` Kirill Yukhin
2020-01-29 21:41 ` Konstantin Osipov [this message]
2020-01-30 7:23 ` Alexander Turenko
2020-01-30 8:21 ` Konstantin Osipov
2020-01-30 11:03 ` Alexander Turenko
2020-01-30 12:16 ` Konstantin Osipov
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=20200129214122.GB31458@atlas \
--to=kostja.osipov@gmail.com \
--cc=alexander.turenko@tarantool.org \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [small] Revert "Free all slabs on region reset"' \
/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