[quote=“Reynald”]You were writing your commands are not taking a long time to execute, less than 3 seconds.
If a command is taking 2 seconds to execute, this means that during all this time, no attribute can be read because there is a locking mechanism in Tango which by default makes it impossible to read an attribute in parallel of executing a command or reading another attribute. This is to simplify the device server programmer’s life and make thread-safe device servers.
So 2 seconds command execution for instance would be a very long execution time in your case if you want to be able to poll your attributes at 200 ms, or even 10 ms!
So please check your commands execution times and ensure they are not the cause for event losses.[/quote]
Hi Reynald,
The command execution time is less. I dont think this is the problem because whenever we have only 1 or 2 device servers, and a client subscribes the change event of spectrum attribute of both device servers, client gets all the events. No event is missed.
The problem is when we increase the number of device servers and a single client.
The spectrum attribute of all the device servers changes simultaneously, so client gets some events and some events are getting missed.
Any suggestion regarding this will be helpful