Make your .NET app run faster
It’s powerful, easy, and **free
Spot slow code
Are you a .NET developer? Would you like your application to run faster? Then use our free profiler to spot you app’s slow code.
Point and go
No source code changes are needed. Just point the profiler to your app, run the modified code, and get a visual report.
Speedup any .NET app
As the only code profiler in the world, our profiler can even handle Compact Framework applications.
C or C++
.NET CF 3.5
.NET CF 2.0
These are the key features of the EQATEC Profiler.
Optimize speed, not memory usage
The EQATEC Profiler is a code profiler, not a memory profiler. So it’s all about making your app run faster, not about tracking objects and memory.
The report will tell you exactly how many times each method was called and how long it took. You can then speedup your application by optimizing just the most expensive methods.
Easy to use
We have focused much on making the profiler and viewer both very easy to use:
You can profile any .NET application with just a few clicks. No source code changes are needed.
The viewer has been designed to make it easy to drill quickly into what really matters: the most expensive methods and their context.
So don’t let the simple look fool you - we take pride in not adding tons of useless options, but instead make tools that simply does “the right thing” by itself.
Profile any .NET app (2.0 and above)
Only code profiler for .NET CF
The profiler was developed specifically to optimize .NET CF apps, and is actually the only existing code profiler for .NET CF in the World as of May, 2008.
The report is stored as a simple file to simplify usage on an embedded device that has no network connectivity.
Low runtime overhead
The overhead depends on the instrumentation-level and the application itself, but typically your app will only run 30% slower and become 30% bigger.
This low overhead means you’re usually able to run your app just like normal, even for timing-critical code.
A command-line version of the profiler enables you to integrate the profiling-step straight into your ordinary build-process, e.g. in MSBuild.
On a 3GHz P4 PC the profiling step typically takes 1 second per 2000 methods, so that’s pretty quick.
You can control the profiler programmatically, too: take a profile-snapshot precisely when needed, not just when your application stops.
You may also use attributes to prevent any method from being profiled or from appearing in the report.
”-and free means crap, right?”
Well, not always. You know, some happy users have actually told us that we ought to charge them for this kind of quality tool. Really, its true!
However, for now we’ve decided not to.