When it comes to application performance, timing is everything. Faster is better than slower—but it’s not always easy to detect when an application is hobbled in some way, or when agents aren’t executing as expected. Teamstudio Profiler lets you see at a glance how every line of your LotusScript is performing, so you can effectively pinpoint bottlenecks without the need for manual testing.
It’s time to put away the stopwatch
The scenarios are familiar to any admin or developer: Simple actions seem to take longer. End users have begun to make a fuss about application performance—or perhaps they’re just stoically putting up with subpar performance because they assume that’s the nature of the beast. Scheduled agents are running slowly—or perhaps not at all (you’re not really sure). Or someone is pointing the finger at Notes as the likely culprit for degraded performance in an application that runs on a combination of technologies.
But what to do? You know that the only way to truly pinpoint the problem is to see how long it takes each line of your LotusScript to execute, but your script libraries are so large you don’t know where to start. Then there’s the risk that you could inadvertently screw up a critical part of your application by adding your own measuring code. So you open the drawer and pull out your trusty stopwatch ...
Viewing Profiler results (click image to enlarge)
A better way to measure and diagnose LotusScript performance
Now imagine that you have a tool that can pore through all of your LotusScript, both simple and complex, and tell you exactly how well your scripts are performing. In a nutshell, that’s what Teamstudio Profiler does. With Profiler, finding the bottleneck is an exact science, not a matter of guesswork. Profiler presents performance data in a simple bar chart, so you can scan a report and quickly locate the laggards in your script. No manual timing statements, no stopwatches. Profiler’s comprehensive reporting gives you the peace of mind (and proof) that every line of code has been tested, and that flawed script won’t plague future generations of an application.
When Profiler is part of your development and testing toolkit, developers can focus on more important tasks than trying to ferret out poor-performing script through trial and error. Used during testing or development, Profiler greatly improves the likelihood that problems are eradicated before they hit production, resulting in solid, efficient applications that do everyone proud.