EQATEC Profiler: An Application Code Profiler for the .NET Compact Framework

| by Abel Avram Follow 9 Followers on May 08, 2008. Estimated reading time: 1 minute |

EQATEC has created a code profiler for applications  written for the .NET Compact Framework. Initially written for their own needs, EQATEC decided to release the profiler to the entire community of .NET Compact Framework developers. This is not a memory usage profiler, but a tool used to detect application bottlenecks, the places in the code where most of processing time is spent.

These are the main features according to EQATEC:

  • Code profiler for optimizing your application's speed/performance, not a memory profiler
  • Very low overhead; typically less than 30% longer runtime and 50% extra code size
  • All .NET 2.0/3.5 Compact Framework (.NET CF) applications can be profiled
  • Command-line version can integrate profiling into your auto build
  • Precise instrumentation, as opposed to sampling profilers
  • Will profile methods, not individual statements
  • Full call-graph details are reported
  • 100% free for all to use

Running this profiler is simple. The application is compiled as usually, then the profiler is used to inject binary code into the assemblies which are to be monitored. The application is then run on the device producing a report which is loaded into the profiler viewer for analysis.

There are some limitations to the profiler according to EQATEC:

  • User-defined generics are not supported. If you define your own generic type of method the resulting assembly currently would not work. Right now the profiler simply skips all assemblies containing generics, but that's pretty annoying. Fixing this has top priority.
  • Recursive methods is reported as sum of the calls. The viewer should be more clever in this respect.
  • Blocking methods, such as Read(), will be counted as the total time, including the time the thread spends being unscheduled and waiting for the call to complete.
  • Strong-name signed assemblies are not supported now. They would have to be re-signed after having been profiled. This feature is currently missing.
  • No debug information is available for the profiled assemblies. It means that you cannot debug the profiled versions - but you would probably not like to do that, anyway.
  • No Visual Studio integration yet. We'd like to create an add-in that will make it even easier to enable profiling your solution's assembly files.

 A video demo of the profiler is available. The profiler can be downloaded here.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

1 Discuss

Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you