You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@storm.apache.org by Nilesh Chhapru <ni...@ugamsolutions.com> on 2014/11/15 08:27:59 UTC

Max Spout Pending Ideal Number?

Hi All,

What number should we keep for max spout pending in ideal scenario, as it is causing the throughput issues.

Regards,
Nilesh Chhapru.

________________________________
---------------------------------------------------------------------------------------Disclaimer----------------------------------------------------------------------------------------------

****Opinions expressed in this e-mail are those of the author and do not necessarily represent those of Ugam. Ugam does not accept any responsibility or liability for it. This e-mail message may contain proprietary, confidential or legally privileged information for the sole use of the person or entity to whom this message was originally addressed. Any review, re-transmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this e-mail in error, please delete it and all attachments from any servers, hard drives or any other media.

Warning: Sufficient measures have been taken to scan any presence of viruses however the recipient should check this email and any attachments for the presence of viruses. Ugam accepts no liability for any damage caused by any virus transmitted by this email. ****

Re: Max Spout Pending Ideal Number?

Posted by Vladi Feigin <vl...@gmail.com>.
hi,

It's matter of fine tuning and depends on your topology , there is no one
gold number. Start from 1K , monitor it. If you see that your topology
supports higher throughput , increase it ... or if it's not, decrease it..

  Vladi

On Sat, Nov 15, 2014 at 9:27 AM, Nilesh Chhapru <
nilesh.chhapru@ugamsolutions.com> wrote:

>  Hi All,
>
>
>
> What number should we keep for max spout pending in ideal scenario, as it
> is causing the throughput issues.
>
>
>
> *Regards*,
>
> *Nilesh Chhapru.*
>
> ------------------------------
>
> ---------------------------------------------------------------------------------------Disclaimer----------------------------------------------------------------------------------------------
>
> ****Opinions expressed in this e-mail are those of the author and do not
> necessarily represent those of Ugam. Ugam does not accept any
> responsibility or liability for it. This e-mail message may contain
> proprietary, confidential or legally privileged information for the sole
> use of the person or entity to whom this message was originally addressed.
> Any review, re-transmission, dissemination or other use of or taking of any
> action in reliance upon this information by persons or entities other than
> the intended recipient is prohibited. If you have received this e-mail in
> error, please delete it and all attachments from any servers, hard drives
> or any other media.
>
> Warning: Sufficient measures have been taken to scan any presence of
> viruses however the recipient should check this email and any attachments
> for the presence of viruses. Ugam accepts no liability for any damage
> caused by any virus transmitted by this email. ****
>