I can't see why it should be blocking. On 14 Nov 2015 01:08, "Isha Arkatkar" <[email protected]> wrote:
> Yes, this is only for inter-container optimization, so we need serialized > tuples. > > The blocking queue is for implementing Publisher-consumer sort of thing, > where publisher will push the data to the queue, And on the buffer server > side, another thread loop will pick this data and put it in data list. > Any suggestions on better ways to implement this mechanism? > > Thanks, > Isha > > On Fri, Nov 13, 2015 at 11:34 AM, Thomas Weise <[email protected]> > wrote: > > > The serialization and buffer server is only used for inter-container > > communication. > > > > On Fri, Nov 13, 2015 at 11:30 AM, Munagala Ramanath <[email protected] > > > > wrote: > > > > > If it is the same container, why bother serializing ? > > > > > > Ram > > > > > > On Fri, Nov 13, 2015 at 11:19 AM, Isha Arkatkar <[email protected]> > > > wrote: > > > > Hi all, > > > > > > > > For APEX-259 (https://malhar.atlassian.net/browse/APEX-259), I am > > > > exploring option of passing serialized tuples from publisher to > buffer > > > > server through a blocking queue. > > > > > > > > Right now, publisher and buffer server reside within the same > > container, > > > > however, communication between the two goes though sockets. We want > to > > > > check if we get any performance benefit by changing this > communication > > to > > > > queue-based one. > > > > > > > > This is in exploration phase right now, but if we do see improvement, > > we > > > > may want to provide it as a pluggable option. > > > > > > > > Please let me know your thoughts! > > > > > > > > Thanks, > > > > Isha > > > > > >
