Not sure if this is helpful, but there is already a utility in Malhar for converting tuples per second to tuples per window. This allows the user to define a property in tuples per second, then the operator can convert that to tuples per window so it emits the correct number of tuples per window.
https://github.com/apache/incubator-apex-malhar/blob/master/library/src/main/java/com/datatorrent/lib/util/time/WindowUtils.java On Wed, Mar 2, 2016 at 10:41 AM, Chinmay Kolhatkar <[email protected]> wrote: > Hi Priyanka, > > Indeed this is a useful feature. > > I believe number bytes consumed per sec can as well translate to number of > tuples consumed per sec. > > If above is correct, won't back pressure that is handled by bufferserver > help in your use case? > > Thanks, > Chinmay. > On 2 Mar 2016 4:49 p.m., "Priyanka Gugale" <[email protected]> > wrote: > > > Many times we need to put bandwidth restrictions or put some limit on > input > > operator for number of bytes to be consumed per second. As I understand > in > > Apex there is no direct support for this feature. > > > > I am planning to write a bandwidth manager which will help in limiting > > bandwidth at Input operator. Let me know if there are any better > > alternative ways. I will soon publish design for Bandwidth Manager I am > > planning to write. > > > > -Priyanka > > >
