Is there a way that I can disable databroadcasting for certain solutions.
This disable should then be the “receiving” event.
I have some solutions that I don’t want to update the forms with most recent values, due to performance issues.
Maybe also an alternative:
Make is possible to disable broadcasting on certain tables.
But when/where you must disable this then?
disabling per solution or per table is not possible.
What kind of performance problems do you get because of broadcast?
Turning off databroadcast does have some implications because our caches on the clients are then not in sync anymore and the only thing to work around that is call
plugins.rawSQL.flushAllClientsCache()
which would be really really bad for performance.
Johan,
The Refresh/Rollback issue http://forum.servoy.com/viewtopic.php?f=4&t=12584&start=0&st=0&sk=t&sd=a
The moment I open once a form containing a foundset that is updating very often (counter), then I see this Refresh/Rollback in the performance log.
Otherwise I have to do rawSQL updates to avoid the databroadcasting, if there is no other solution for that
Martin
you see that the performance of the refresh query for that specific record takes long.
But is the user really affected… do you notice it in that client
I do notice it, because the headless client is running much longer than expected.
In the client I can see it, because I see the counter skipping numbers.
That is not really a problem. The faster it counts, the better it is
The problem is that these Refresh/Rollback show me a long delay. 35 minutes in a 4 hour process is almost 15% waiting time
if you are updating records at that speed, can’t you up the transaction then?
Must it really be a transaction per update of 1 record?
Because if you would do it in a way bigger transaction window your complete speed would get an enormous boost.