From: Arkadi Colson <arkadi@smartbit.be>
To: Eric Wong <e@80x24.org>
Cc: "cmogstored-public@bogomips.org" <cmogstored-public@bogomips.org>
Subject: Re: Heavy load
Date: Wed, 18 Dec 2019 07:56:24 +0000 [thread overview]
Message-ID: <06b931d9-fc30-ba20-6b02-ddd2b9120766@smartbit.be> (raw)
In-Reply-To: <20191217194205.GA31282@dcvr>
On 17/12/19 20:42, Eric Wong wrote:
> Arkadi Colson <arkadi@smartbit.be> wrote:
>>> Any idea? If you need more info, please just ask!
>> We are having about 192 devices spread over about 23 cmogstored hosts.
>> Each device is one disk with one partition...
>>> How many "/devXYZ" devices do you have? Are they all
>>> on different partitions?
> OK, thanks. I've only got a single host nowadays with 3
> rotational HDD. Most I ever had was 20 rotational HDD on a
> host but that place is out-of-business.
>
> Since your build did not include -ggdb3 with debug_info by default;
> I wonder if there's something broken in your build system or
> build scripts... Which compiler are you using?
>
> Can you share the output of "ldd /path/to/cmogstored" ?
root@mogstore:~# ldd /usr/bin/cmogstored
linux-vdso.so.1 (0x00007fff6584b000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007f634a7f2000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f634a453000)
/lib64/ld-linux-x86-64.so.2 (0x00007f634ac50000)
> Since this is Linux, you're not using libkqueue, are you?
>
> Also, which Linux kernel is it?
In fact it's a clean debian stretch installation with htis kernel:
root@mogstore:~# uname -a
Linux mogstore 4.9.0-11-amd64 #1 SMP Debian 4.9.189-3+deb9u2
(2019-11-11) x86_64 GNU/Linux
>
> Are you using "server aio_threads =" via mgmt interface?
I don't think so. How can I verify this?
>
> Are you using the undocumented -W/--worker-processes or
> -M (multi-config) option(s?)
I don't think so: Config looks like this:
httplisten = 0.0.0.0:7500
mgmtlisten = 0.0.0.0:7501
maxconns = 10000
docroot = /var/mogdata
daemonize = 1
server = none
>
> Is your traffic read-heavy or write-heavy?
We saw peaks of 3Gb traffic on the newest cmogstore when marking one
host dead...
> I just tested 10s parallel PUTs and 100s of parallel GETs
> without any problems.
next prev parent reply other threads:[~2019-12-18 7:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 13:54 Heavy load Arkadi Colson
2019-12-11 17:06 ` Eric Wong
2019-12-12 7:30 ` Arkadi Colson
2019-12-12 7:59 ` Eric Wong
2019-12-12 19:16 ` Eric Wong
2019-12-17 7:40 ` Arkadi Colson
2019-12-17 8:43 ` Eric Wong
2019-12-17 8:57 ` Arkadi Colson
2019-12-17 19:42 ` Eric Wong
2019-12-18 7:56 ` Arkadi Colson [this message]
2019-12-18 17:58 ` Eric Wong
2020-01-06 9:46 ` Arkadi Colson
2020-01-08 3:35 ` Eric Wong
2020-01-08 9:40 ` Arkadi Colson
2020-01-30 0:35 ` Eric Wong
2020-03-03 15:46 ` Arkadi Colson
2019-12-17 7:41 ` Arkadi Colson
2019-12-17 8:31 ` Eric Wong
2019-12-17 8:43 ` Arkadi Colson
2019-12-17 8:50 ` Eric Wong
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
List information: https://yhbt.net/cmogstored/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=06b931d9-fc30-ba20-6b02-ddd2b9120766@smartbit.be \
--to=arkadi@smartbit.be \
--cc=cmogstored-public@bogomips.org \
--cc=e@80x24.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/cmogstored.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).