Case study:

Trouble shooting performance

The problem:

Our customer had problems one day when all their applications slowed down. Their Indian office was down for the day, but their applications shouldn’t be connecting to that office, so they didn’t know what was wrong.

Trouble shooting performance issues

The solution:

After you’ve traced a job in Breeze, you can see how programs have been executed over time by looking at the timeline.

You can also see what a program did at what time. This can help you work out the order in which scripts were called or the amount of time spent accessing the network.

The result:

The customer traced their applications with Breeze and found that, after connecting to local license servers, their simulation software was still trying to connect to the Indian office. It hung for a few seconds before timing out, causing the slow down across their whole system.