Is there any pre/post-condition performance tips?
We may want to implement the post-condition for work item changes(create/modify/change status) to send message to another system when work item updates. I know the work item updates event frequency may be large according to the usage, if I really implement my customized post-condition for all work item updates to transfer message to another system, is there any performance tips need to pay attention? Thanks very much!
Accepted answer
There is only so much processing power available. There is no free lunch. Operational behavior usually checks if it has to run and tries to exit as fast as possible with as few work as possible.
If it is in the UI thread the user will have to wait or you run it in a background job. Or you decide to go for a notifier task, if the response does not have to be immediate. In any way, the task will have an impact on the system load, based on the amount of work that needs to be done.
If it is in the UI thread the user will have to wait or you run it in a background job. Or you decide to go for a notifier task, if the response does not have to be immediate. In any way, the task will have an impact on the system load, based on the amount of work that needs to be done.