I am assuming that's what the proposal has based on the initial email. On 14 Nov 2015 01:00, "Thomas Weise" <[email protected]> wrote:
> Yes, but why do we need another blocking queue? > > On Fri, Nov 13, 2015 at 11:21 AM, Atri Sharma <[email protected]> wrote: > > > Apart from file I/O overhead saving , what else can you see that will be > > saved? > > > > IMO a blocking queue might add an additional overhead and might tend to > > localise the bottleneck to a single queue. Just my 2c... > > On 14 Nov 2015 00:49, "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 > > > > > >
