batching will be eliminated in the new messaging system.
>
>
>
> -roshan
>
>
>
>
>
> *From: *Adam Meyerowitz
> *Reply-To: *"user@storm.apache.org"
> *Date: *Tuesday, June 6, 2017 at 2:36 PM
> *To: *"user@storm.apache.org"
> *Subject: *
n the new messaging system.
-roshan
From: Adam Meyerowitz
Reply-To: "user@storm.apache.org"
Date: Tuesday, June 6, 2017 at 2:36 PM
To: "user@storm.apache.org"
Subject: Re: LMAX queue batch size
Hi Roshan, these metrics are for an intermediate bolt and they are for the
inbou
If you can feed it one event at a time and each time see how these metrics are
changing it might give a clue.
-roshan
From: Adam Meyerowitz
Reply-To: "user@storm.apache.org"
Date: Tuesday, June 6, 2017 at 2:36 PM
To: "user@storm.apache.org"
Subject: Re: LMAX queue batch si
/ intermediate bolt / spout ?
>
> Are those metrics for the inbound or the outbound DisruptorQ of the
> spout/bolt?
>
> -roshan
>
>
>
>
>
>
>
> *From: *Adam Meyerowitz
> *Reply-To: *"user@storm.apache.org"
> *Date: *Tuesday, June 6, 2017 at 7:
?
Are those metrics for the inbound or the outbound DisruptorQ of the spout/bolt?
-roshan
From: Adam Meyerowitz
Reply-To: "user@storm.apache.org"
Date: Tuesday, June 6, 2017 at 7:12 AM
To: "user@storm.apache.org"
Subject: Re: LMAX queue batch size
To make things a litt
To make things a little bit more specific this is the kind of thing we are
seeing.. I have chopped out some line, etc to make it more readable.
Note that during this one minute interval the read_pos went from
177914 to 178522
which is a difference of 608 yet we processed 4140 tuples based on the
e
Currently we are using 1.0.1.
Thanks for the video. It definitely clarifies the lower level details of
the queueing.
Quick followup question. In the case where the disruptor queue is full and
data ends up in the overflow list, you mentioned that **one element** in
that list can be multiple tuple
AM> So the difference in the read and write queue positions will be 100 then,
correct?
Only if the diff was 0 prior to the publish. More accurately… the diff between
the read and write positions will increase by 100 after the publish.
AM> Empirically what we are seeing would lead us to belie
han
>
>
>
>
>
> *From: *Adam Meyerowitz
> *Reply-To: *"user@storm.apache.org"
> *Date: *Friday, June 2, 2017 at 9:14 AM
> *To: *"user@storm.apache.org"
> *Subject: *Re: LMAX queue batch size
>
>
>
> Hi Roshan, thanks!
>
> Mayb
te: Friday, June 2, 2017 at 9:14 AM
To: "user@storm.apache.org"
Subject: Re: LMAX queue batch size
Hi Roshan, thanks!
Maybe an example will clarify what I'm after.
Let's say that there is a batch of 100 items to be written to the disruptor
queue and those are to be written
ritten to the Q in one go.
>
>
>
> roshan
>
>
>
> *From: *Adam Meyerowitz
> *Reply-To: *"user@storm.apache.org"
> *Date: *Thursday, June 1, 2017 at 1:47 PM
> *To: *"user@storm.apache.org"
> *Subject: *LMAX queue batch size
>
>
>
> Hello, ca
;user@storm.apache.org"
Date: Thursday, June 1, 2017 at 1:47 PM
To: "user@storm.apache.org"
Subject: LMAX queue batch size
Hello, can someone clarify how the disruptor queue batch size setting,
TOPOLOGY_DISRUPTOR_BATCH_SIZE,
impacts insertion? More specifically is each disruptor queue entry
Hello, can someone clarify how the disruptor queue batch size setting,
TOPOLOGY_DISRUPTOR_BATCH_SIZE,
impacts insertion? More specifically is each disruptor queue entry a
single item or a list of items up to the configured batch size?
Thanks.
13 matches
Mail list logo
