I'm seeing some rados runs stuck on peering messages not getting sent
by the async messenger: http://tracker.ceph.com/issues/13213. Can you
take a look?
-Sam
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.
On Fri, Aug 28, 2015 at 2:35 PM, Jianhui Yuan wrote:
> Hi Haomai,
>
> when we use async messenger, the client(as: ceph -s) always stuck in
> WorkerPool::barrier for 30 seconds. It seems the wakeup don't work.
What's the ceph version and os version? It should be a bug w
t; job(http://pulpito.ceph.com/haomai-2015-08-27_04:09:28-rados-master-distro-basic-multi/)
> and the result seemed ok to me.
>
> On Tue, Aug 25, 2015 at 9:22 AM, Haomai Wang wrote:
> > On Tue, Aug 25, 2015 at 5:28 AM, Sage Weil wrote:
> >> Hi Haomai,
> >>
> >> How did
I ran a random
job(http://pulpito.ceph.com/haomai-2015-08-27_04:09:28-rados-master-distro-basic-multi/)
and the result seemed ok to me.
On Tue, Aug 25, 2015 at 9:22 AM, Haomai Wang wrote:
> On Tue, Aug 25, 2015 at 5:28 AM, Sage Weil wrote:
>> Hi Haomai,
>>
>> How did y
ct in async may have
> some problem that can't be sloved now, or we may just support this feature?
>
Yep, async messenger should avoid all potential blocking point. In
msg/async/net_handler.cc, we already have
"NetHandler::nonblock_connect" impl. Long ago because nonblock co
On Tue, Aug 25, 2015 at 5:28 AM, Sage Weil wrote:
> Hi Haomai,
>
> How did your most recent async messenger run go?
>
> If there aren't major issues, we'd like to start mixing it in with the
> regular rados suite by doing 'ms type = random'...
>From last
Hi Haomai,
How did your most recent async messenger run go?
If there aren't major issues, we'd like to start mixing it in with the
regular rados suite by doing 'ms type = random'...
sage
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
t
Mail original -
De: "Haomai Wang"
À: "aderumier"
Cc: "Mark Nelson" , "ceph-devel"
Envoyé: Mercredi 29 Avril 2015 08:21:36
Objet: Re: async messenger small benchmark result
Still not, we currently only focus on bug fix and stable purpose. But
I think p
lson"
> À: "aderumier" , "ceph-devel"
>
> Envoyé: Mardi 28 Avril 2015 15:48:51
> Objet: Re: async messenger small benchmark result
>
> Hi Alex,
>
> Thanks! So far we've gotten a report that asyncmesseneger was a little
> slower than simpl
Mail original -
De: "Mark Nelson"
À: "aderumier" , "ceph-devel"
Envoyé: Mardi 28 Avril 2015 15:48:51
Objet: Re: async messenger small benchmark result
Hi Alex,
Thanks! So far we've gotten a report that asyncmesseneger was a little
slower than simple mess
er vs async messenger
This is with 2 osd, and 15 fio jobs on a single rbd volume
simple messager : 345kiops
async messenger : 139kiops
Regards,
Alexandre
simple messenger
---
^Cbs: 15 (f=15): [r(15)] [0.0% done] [1346MB/0KB/0KB /s] [345K/0/0 iops] [eta
59d:13h:32m:43s
Thanks for your benchmark!
Yeah, async messenger exists a bottleneck when meet high concurrency
and iops. Because it exists a annoying lock related to crc calculate.
Now my main job is focus on passing on qa tests for async messenger.
If no failed tests, I will solve this problem.
On Tue, Apr 28
Hi,
here a small bench 4k randread of simple messenger vs async messenger
This is with 2 osd, and 15 fio jobs on a single rbd volume
simple messager : 345kiops
async messenger : 139kiops
Regards,
Alexandre
simple messenger
---
^Cbs: 15 (f=15): [r(15)] [0.0% done] [1346MB/0KB
df45af01cf]
> 6: (()+0x6b50) [0x7fdf4a1f2b50]
> 7: (clone()+0x6d) [0x7fdf4969c7bd]
> NOTE: a copy of the executable, or `objdump -rdS ` is needed to
> interpret this.
> terminate called after throwing an instance of 'ceph::FailedAssertion'
> Abandon
> - Mail ori
could you run "ceph -w --debug-ms=10/10" ?
On Tue, Nov 4, 2014 at 5:29 AM, Alexandre DERUMIER wrote:
> Hi,
>
> I'm try to test the async messenger (ms_type = async) with last master,
> and I have an assert on line 1046 of AsyncConnection.cc.
> (I don't have tri
Hi,
I'm try to test the async messenger (ms_type = async) with last master,
and I have an assert on line 1046 of AsyncConnection.cc.
(I don't have tried yet with previous builds)
no tuning in ceph.conf, only the ms_type = async.
#ceph -w
msg/async/AsyncConnection.cc: In fun
On Wed, 22 Oct 2014, Somnath Roy wrote:
> Sage,
> So, with krbd as client, should I use 'ms_type = random' in the cluster side
> to test Async messenger in the cluster side?
> BTW, what this option does ? It will pick Async first and fall back to old
> messenger in ca
Sage,
So, with krbd as client, should I use 'ms_type = random' in the cluster side to
test Async messenger in the cluster side?
BTW, what this option does ? It will pick Async first and fall back to old
messenger in case any problem ?
Thanks & Regards
Somnath
-Original Mes
is true (by doing QA on mixes old both messenger implementations).
sage
>
> On Thu, Oct 23, 2014 at 1:18 AM, Somnath Roy wrote:
> > Thanks Haomai, I will try this branch out.
> > BTW, will it be compatible with the client which is not using this async
> > mes
ent which is not using this async
> messenger for example krbd ?
>
> Regards
> Somnath
>
> -Original Message-
> From: Haomai Wang [mailto:haomaiw...@gmail.com]
> Sent: Wednesday, October 22, 2014 10:02 AM
> To: Somnath Roy
> Cc: ceph-devel@vger.kernel.org
>
Thanks Haomai, I will try this branch out.
BTW, will it be compatible with the client which is not using this async
messenger for example krbd ?
Regards
Somnath
-Original Message-
From: Haomai Wang [mailto:haomaiw...@gmail.com]
Sent: Wednesday, October 22, 2014 10:02 AM
To: Somnath Roy
ms_type = async is needed to add [global] section in ceph.conf
No other options are needed
On Thu, Oct 23, 2014 at 12:02 AM, Somnath Roy wrote:
> Hi Haomai/Sage,
>
> I just figured it out that Async messenger is not yet in master. So, I didn't
> really test the async messen
Hi Haomai/Sage,
I just figured it out that Async messenger is not yet in master. So, I didn't
really test the async messenger :-(
I saw here is the pull request.
https://github.com/ceph/ceph/pull/2768
I want to test this out and I have some questions regarding this.
1. The branch I s
>>Alexandre,
>>Here is my config..
Thanks Sommath !
- Mail original -
De: "Somnath Roy"
À: "Haomai Wang"
Cc: ceph-devel@vger.kernel.org
Envoyé: Dimanche 19 Octobre 2014 08:15:57
Objet: RE: The Async messenger benchmark with latest master
ge_cap = 0
osd_enable_op_tracker = false
Thanks & Regards
Somnath
-Original Message-
From: Haomai Wang [mailto:haomaiw...@gmail.com]
Sent: Saturday, October 18, 2014 10:15 PM
To: Somnath Roy
Cc: ceph-devel@vger.kernel.org
Subject: Re: The Async messenger benchmark with
Thanks Somnath!
I have another simple performance test for async messenger:
For 4k object read, master branch used 4.46s to complete tests, async
Messenger used 3.14s
For 4k object write, master branch used 10.6s to complete, async
Messenger used 6.6s!!
Detailf results see below, 4k object read
Hi Somnath,
Results seem promising indeed :)
Can you share your ceph.conf ?
- Mail original -
De: "Somnath Roy"
À: ceph-devel@vger.kernel.org
Envoyé: Vendredi 17 Octobre 2014 22:37:55
Objet: The Async messenger benchmark with latest master
Hi Sage/Haomai,
I did some
Hi Sage/Haomai,
I did some 4K Random Read benchmarking with latest master having Async
messenger changes and result looks promising.
My configuration:
-
1 node, 8 SSDs, 8OSDs, 3 pools , each has 3 images. ~2000 Pg cluster wide
Cpu : Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
28 matches
Mail list logo
