From: Konstantin Osipov <kostja.osipov@gmail.com> To: Kirill Yukhin <kyukhin@tarantool.org>, lvasiliev <lvasiliev@tarantool.org>, alexander.turenko@tarantool.org, tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH 3/6] iproto: Add negotiation phase Date: Thu, 26 Mar 2020 16:31:15 +0300 [thread overview] Message-ID: <20200326133115.GA11411@atlas> (raw) In-Reply-To: <20200326131954.GC8031@atlas> * Konstantin Osipov <kostja.osipov@gmail.com> [20/03/26 16:19]: > A vshard based cluster with 20 router nodes and 20 storage nodes, > 32 core each, will have 20*32*32*16 connections. These are only internal connections maintained by vshard. Replication adds miniscule 32*20*2 connection to that. Any monitoring will be likely establishing a new connection for every monitoring request, 32*40 connections per second. Any quality of service feature, like separating oltp and analytical traffic, could easily require doubling it, since all prioritized work has to use its own transport infrastructure. Any network partitioning event will lead to avalanche like re-establishment of these connections. One can ignore performance concerns, of course, given there has been a foundation of scrupulous accounting for every bit and every CPU cycle, but not very long. > A 20-40 node cluster is not big by any means. > > -- > Konstantin Osipov, Moscow, Russia -- Konstantin Osipov, Moscow, Russia
next prev parent reply other threads:[~2020-03-26 13:31 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-24 12:45 [Tarantool-patches] [PATCH 0/6] Extending error functionality Leonid Vasiliev 2020-03-24 12:45 ` [Tarantool-patches] [PATCH 1/6] error: Add a Lua backtrace to error Leonid Vasiliev 2020-04-05 22:14 ` Vladislav Shpilevoy 2020-04-08 13:56 ` Igor Munkin 2020-03-24 12:46 ` [Tarantool-patches] [PATCH 2/6] error: Add the custom error type Leonid Vasiliev 2020-04-05 22:14 ` Vladislav Shpilevoy 2020-03-24 12:46 ` [Tarantool-patches] [PATCH 3/6] iproto: Add negotiation phase Leonid Vasiliev 2020-03-24 20:02 ` Konstantin Osipov 2020-03-25 7:35 ` lvasiliev 2020-03-25 8:42 ` Konstantin Osipov 2020-03-25 10:56 ` Eugene Leonovich 2020-03-25 11:13 ` Konstantin Osipov 2020-03-26 11:37 ` lvasiliev 2020-03-26 11:18 ` lvasiliev 2020-03-26 12:16 ` Konstantin Osipov 2020-03-26 12:54 ` Kirill Yukhin 2020-03-26 13:19 ` Konstantin Osipov 2020-03-26 13:31 ` Konstantin Osipov [this message] 2020-03-26 21:13 ` Alexander Turenko 2020-03-26 21:53 ` Alexander Turenko 2020-03-27 8:28 ` Konstantin Osipov 2020-03-26 23:35 ` Alexander Turenko 2020-03-27 8:39 ` Konstantin Osipov 2020-03-24 12:46 ` [Tarantool-patches] [PATCH 4/6] error: Add extended error transfer format Leonid Vasiliev 2020-03-24 12:46 ` [Tarantool-patches] [PATCH 5/6] error: Add test for extended error Leonid Vasiliev 2020-03-24 12:46 ` [Tarantool-patches] [PATCH 6/6] error: Transmit an error through IPROTO_OK as object Leonid Vasiliev 2020-03-27 23:11 ` [Tarantool-patches] [PATCH 0/6] Extending error functionality lvasiliev 2020-03-28 13:54 ` Alexander Turenko 2020-03-30 10:48 ` lvasiliev 2020-04-01 15:35 ` Alexander Turenko
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=20200326133115.GA11411@atlas \ --to=kostja.osipov@gmail.com \ --cc=alexander.turenko@tarantool.org \ --cc=kyukhin@tarantool.org \ --cc=lvasiliev@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 3/6] iproto: Add negotiation phase' \ /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