Subject | Re: [firebird-support] Performance of events |
---|---|
Author | Daniel Albuschat |
Post date | 2009-12-15T13:58:37Z |
2009/12/15 Douglas Tosi <douglasht@...>
thanks for sharing your experience!
Firebird 1.0 is quite old now. I'm only using Firebird 1.5 myself, but I
guess that much (could) have changed for Firebird 2.x.
On the other hand, I have the feeling that events are a feature that don't
receive much love from the developers.
Perhaps some dev might be able to tell us more.
Daniel
--
eat(this); // delicious suicide
[Non-text portions of this message have been removed]
> Hello Daniel,Hi Douglas,
>
> On Tue, Dec 15, 2009 at 10:14 AM, Daniel Albuschat
> <d.albuschat@... <d.albuschat%40gmail.com>> wrote:
> > Are events something meant to be used rarely, or is
> > something like 10 posted events per second with 100 different clients
> > listening to potentially hundreds of events per connection feasible?
>
> I've used events in the past, including heavy load scenarios with 200
> clients and hundreds of events per minute. I'd recommend against it.
> Random server crashes, zombie attachments and hanging clients were too
> frequent.
> This was in the firebird 1.0 era and things may have improved of course.
>
> One thing to be careful with event-based auto update: If 100 clients
> get an event saying 'refresh query x', you don't want them all to
> refresh at the same time.
>
thanks for sharing your experience!
Firebird 1.0 is quite old now. I'm only using Firebird 1.5 myself, but I
guess that much (could) have changed for Firebird 2.x.
On the other hand, I have the feeling that events are a feature that don't
receive much love from the developers.
Perhaps some dev might be able to tell us more.
Daniel
--
eat(this); // delicious suicide
[Non-text portions of this message have been removed]