From: Konstantin Osipov via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v3] wal: introduce limits on simultaneous writes
Date: Wed, 10 Mar 2021 11:18:04 +0300 [thread overview]
Message-ID: <20210310081804.GA87351@starling> (raw)
In-Reply-To: <26fde1bf-a972-fe03-fffe-818839718394@tarantool.org>
* Vladislav Shpilevoy via Tarantool-patches <tarantool-patches@dev.tarantool.org> [21/03/09 23:44]:
> Hi! Thanks for the patch!
>
> LGTM.
>
> > https://github.com/tarantool/tarantool/issues/5536
> > https://github.com/tarantool/tarantool/tree/sp/gh-5536-replica-oom
I don't understand why you need two parameters, size and len. What
difference does it make how many requests are in the queue? The
queue is IO and memory bound, not CPU bound, at least not more cpu
bound than any other subsystem.
Pushing the problem to the user by forcing them to choose not one,
but two configuration values is poor design. How am I supposed to
know what is the right value for the option?
I guess don't know it either - the patch was not followed by
a benchmark which would prove the selected defaults are optimal.
Tarantool has an incoming throttling limit which makes the whole
system work like a clock: it's the fiber pool size and net msg
size. They were carefully selected after days and weeks of
testing.
--
Konstantin Osipov, Moscow, Russia
next prev parent reply other threads:[~2021-03-10 8:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 19:35 Serge Petrenko via Tarantool-patches
2021-02-24 19:40 ` Serge Petrenko via Tarantool-patches
2021-02-25 13:05 ` Konstantin Osipov via Tarantool-patches
2021-02-26 0:57 ` Vladislav Shpilevoy via Tarantool-patches
2021-02-26 7:18 ` Konstantin Osipov via Tarantool-patches
2021-02-26 20:23 ` Vladislav Shpilevoy via Tarantool-patches
2021-02-26 21:20 ` Konstantin Osipov via Tarantool-patches
2021-02-26 22:44 ` Vladislav Shpilevoy via Tarantool-patches
2021-02-27 13:27 ` Konstantin Osipov via Tarantool-patches
2021-03-01 19:15 ` Serge Petrenko via Tarantool-patches
2021-03-01 21:46 ` Konstantin Osipov via Tarantool-patches
2021-02-26 0:56 ` Vladislav Shpilevoy via Tarantool-patches
2021-03-01 19:08 ` Serge Petrenko via Tarantool-patches
2021-03-01 22:05 ` Vladislav Shpilevoy via Tarantool-patches
2021-03-02 17:51 ` Serge Petrenko via Tarantool-patches
2021-03-03 20:59 ` Vladislav Shpilevoy via Tarantool-patches
2021-03-09 15:10 ` Serge Petrenko via Tarantool-patches
2021-03-09 19:49 ` Vladislav Shpilevoy via Tarantool-patches
2021-03-10 8:18 ` Konstantin Osipov via Tarantool-patches [this message]
2021-03-12 17:10 ` Serge Petrenko via Tarantool-patches
2021-03-13 19:14 ` Konstantin Osipov via Tarantool-patches
2021-03-15 23:42 ` Vladislav Shpilevoy via Tarantool-patches
2021-03-16 6:45 ` Konstantin Osipov via Tarantool-patches
2021-03-16 20:27 ` Vladislav Shpilevoy via Tarantool-patches
2021-03-16 10:19 ` Serge Petrenko via Tarantool-patches
2021-03-16 20:48 ` Vladislav Shpilevoy via Tarantool-patches
2021-03-17 12:14 ` Serge Petrenko via Tarantool-patches
2021-03-17 21:02 ` Vladislav Shpilevoy via Tarantool-patches
2021-03-19 11:32 ` Serge Petrenko via Tarantool-patches
2021-03-19 15:36 ` Kirill Yukhin 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=20210310081804.GA87351@starling \
--to=tarantool-patches@dev.tarantool.org \
--cc=kostja.osipov@gmail.com \
--cc=v.shpilevoy@tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v3] wal: introduce limits on simultaneous writes' \
/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