Subject | AW: [firebird-support] Performance of events |
---|---|
Author | Christian Waldmann |
Post date | 2009-12-15T17:08:06Z |
I am using events with no problems with FB 1.5 (VCL Interbase components) and upgraded now to FB 2.1.3 (Devart IBDAC components).
To get the events trough the firewall, I set RemoteAuxPort = 3051 in firebird.conf.
The events keep the user applications up to date. Some events are generated in triggers and some are sent by the application.
I have never missed any events.
For me, events are a very good design tool. No polling for changes is required, and reactions occur as fast as possible.
Best regards
Christian
Von: firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com] Im Auftrag von Daniel Albuschat
Gesendet: Dienstag, 15. Dezember 2009 13:15
An: firebird-support@yahoogroups.com
Betreff: [firebird-support] Performance of events
Hello,
I'm currently widely adopting the usage of events to realize a live
update on all clients when data has been changed from another client.
Does anybody have experience with posting and registering for a lot of
events and it's impacts?
The current usage of event is one posted event every few seconds, with
at least one to five clients listening for that event. That's not much
and I am planning to add much more "event-traffic", but I've noticed
that fbserver utilized the CPU to 100% today and yesterday and I'm not
sure, why. 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?
Could it potentially slow down the server because of dificulties
regarding transaction isolation?
Any hint, suggestion or experience would be highly appreciated.
Greetings,
Daniel Albuschat
--
eat(this); // delicious suicide
[Non-text portions of this message have been removed]
To get the events trough the firewall, I set RemoteAuxPort = 3051 in firebird.conf.
The events keep the user applications up to date. Some events are generated in triggers and some are sent by the application.
I have never missed any events.
For me, events are a very good design tool. No polling for changes is required, and reactions occur as fast as possible.
Best regards
Christian
Von: firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com] Im Auftrag von Daniel Albuschat
Gesendet: Dienstag, 15. Dezember 2009 13:15
An: firebird-support@yahoogroups.com
Betreff: [firebird-support] Performance of events
Hello,
I'm currently widely adopting the usage of events to realize a live
update on all clients when data has been changed from another client.
Does anybody have experience with posting and registering for a lot of
events and it's impacts?
The current usage of event is one posted event every few seconds, with
at least one to five clients listening for that event. That's not much
and I am planning to add much more "event-traffic", but I've noticed
that fbserver utilized the CPU to 100% today and yesterday and I'm not
sure, why. 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?
Could it potentially slow down the server because of dificulties
regarding transaction isolation?
Any hint, suggestion or experience would be highly appreciated.
Greetings,
Daniel Albuschat
--
eat(this); // delicious suicide
[Non-text portions of this message have been removed]