Monday, January 7, 2013

How the Fastest Got Even Faster

FasterYes, we did it again. We managed to make ITRP faster still. Let me explain what we have done this time to bring more joy to IT specialists and service desk analysts (and to make organizations a little more efficient, of course).

There are some transactions that trigger the generation of multiple emails. For example, when a new request is registered and this request is assigned to a team that does not have a coordinator, then each member of this team will receive an email notification. The requester will receive a different notification, and if the request was submitted on behalf of someone else, then this person will get yet another notification. Each email is generated separately in the preferred language of the receiver.

It only takes a few milliseconds to generate each email, but when the team has many members, this can add up. A similar situation can occur when a change is completed, as this causes a notification to be sent to each person whose request or problem was resolved by the implementation of the change.

Rather than making users wait until all the notifications have been generated, users can now continue their work as soon as the generation of the email has been scheduled.

This can shave a full second off of a transaction in extreme cases. And because the generation of these messages is now handled by a separate server, this has reduced the workload of the servers that people are working on. So this performance improvement does not just benefit the people performing such transactions; it has made ITRP a little faster for everyone.