Hi, +1 for unbounded, let the GC take care of it and log periodically when its size becomes significant so that anyone wondering why their JVM is consuming so much GC time gets a clue as to the cause, without having to perform heap dumps, thread dumps or jvm probes.
(but ideally all queues would have simple, efficient, metrics that can be monitored all the time in production, not just by someone connecting a JMX console or Web Console) Best Regards Ian On 17 June 2015 at 09:56, Chetan Mehrotra <chetan.mehro...@gmail.com> wrote: > Just ensure that your Observer is fast as its invoked the critical path. > > This would probably end up with a design similar to Background > Observer. May be better option would be to allow BO have non bounded > queue. > Chetan Mehrotra > > > On Wed, Jun 17, 2015 at 2:05 PM, Carsten Ziegeler <cziege...@apache.org> > wrote: > > Ok, just to recap. In Sling we can implement the Observer interface (and > > not use the BackgroundObserver base class). This will give us reliably > > user id for all local events. > > > > Does anyone see a problem with this approach? > > > > Carsten > > -- > > Carsten Ziegeler > > Adobe Research Switzerland > > cziege...@apache.org >
