After preparing my presentation and having many déjà vus, our SpeedTrace dot.net profiler is ready to show its capabilities and features again. If you are planning a trip to Germany in January, why don’t you pay us a visit and meet us at the booth. I would be glad to talk to you!
You can find more information about our presentaion "Efficient analysis of dot.NET applications with SpeedTrace" here at OOP – Software meets Business.
Have you ever been in a situation or place where the first thing that flashes your mind is "It’s a déjà vu?" According to definition, déjà vu is an internal sense of a person who suddenly feels that he/she has already experienced the present noteworthy situation at some point in the past.
What about having déjà vus when developing and profiling your dot.net applications? I have been looking for information these days for the next conference titled "OOP Software meets Business", taking place in Germany and dealing with the performance of dot.net applications in relation to dot.net profilers. Recently, I came across the article “Tuning .NET Application Performance” from the msdn, and all of a sudden realized that, although written in May 2004, it demonstrated to me that many things have not changed much since then.
What caught my attention was the section "Performance Tuning Process" which states almost exactly what I wanted to say at the conference, of course, with different words.
If you want to eliminate bottlenecks in your dot.net applications you need to be iterative. However, being iterative is a time-consuming task that not all of us can afford due to the usual set cumpolsory project milestones (deadlines).
If you take a close look to the activities in Section 2 and 3 of the article, that’s where I always say our SpeedTrace dot.net profiler can be used with best results. First, look at "Collect Data"; it is said that we need to simulate load and capture metrics — excellent — our dot.net profiler will record your information to help you later with the activity in Section 3, "Analyse Results". That is where you identify performance issues and bottlenecks. How? — By using our dot.net profiler, of course.
However, we have not yet finished at this point, since the rest of the activities, "Configure", and "Test and Measure", need to undergo tuning in order to re-iterate the whole cycle.
So you can see that our SpeedTrace dot.net profiler will accompany you systematically during your whole dot.net development process.
The next time you start a new dot.net project, don’t forget to purchase your SpeedTrace toolkit so you can streamline your development and application with the right guidelines by using a really good dot.net profiler right from the outset. You won’t regret it!
Microsoft released the .NET Framework 3.5 on Monday, November 19, 2007.
We have installed and tested the SpeedTrace dot.NET Profiler against the new .NET Framework 3.5. During preliminary tests, SpeedTrace performed properly and no errors were detected. We will inform you in case any changes are made.
We have recently released a maintenance for SpeedTrace dot.NET Profiler 3.2 — v3.2.14 32-bit and 64-bit versions.
These two versions are available here in the SpeedTrace blog or under http://www.ipcas.com/trace-and-profile/download.html
This release contains several improvements, few minor fixes and additional features.
In regard to the new additional features, you can now profile multiple processes by having several instances of SpeedTrace recording your running processes at the same time. Moreover, you won’t have to contend anymore with sudden terminations of dot.NET processes without yielding information. Now, you’ll also be able to generate trace output from terminated processes without any hassle.
We would like to thank you for all your interest in SpeedTrace during the dot.Net Prio.Conference 2007 that took place in Baden-Baden, Germany. Likewise, our special thanks go to all the people present at our presentation "Efficient Analysis of dot.NET Applications with SpeedTrace Profiler". We hope this conference was informative.
In this first article, we want to exemplify the strong points of SpeedTrace by explaining the importance of having a dot.net profiler and tracer in one.
With its profiler, SpeedTrace traces your application first and then performs the profiling process (i.e. the aggregations) later. This sets SpeedTrace apart from all its competitors, since it retains the time dimension, providing the real and accurate information for every single call.
With its tracer, SpeedTrace enables any dot.net application to register and update large numbers of performance counters in runtime. By collecting them first, SpeedTrace dot.net provides the flexibility for subsequent data analyses helping you to not only identify performance weaknesses, but also to detect bugs such as deadlocks, software design faults, and resource or data flaw problems.
As stated before, bug-trapping is important, however, bug-trapping and performing dot.net analyses can also become a very time-consuming task. However, if the dot.net developer uses SpeedTrace to locate bugs and flaws during the early coding and testing stages, this will put him in a position to accurately trap and fix consistently throughout the development cycle and thus save time and improve quality sustantially!
With SpeedTrace it is basically a matter of a few clicks to turn a developer’s desktop into a workstation that also profiles, tests and quantifies the effects of application code performance within dot.net applications.
Be more productive! SpeedTrace will help you to move away from purely reactive application performance to the far more desirable preventive approach. Achieve higher quality and faster application deployment by ensuring that the dot.net code is sufficiently robust and optimized right from the outset. Be proactive — use SpeedTrace!
This blog is intended to work as a platform for the dot.net development arena aimed at providing the means for best practices in your daily dot.net development work.
We would also like to introduce SpeedTrace, specially designed to profile and trace dot.net applications. Due to its small overhead and its warp speed trace engine, it just happens to be the most accurate and efficient profiler on the market.
This tool can be used not only as a profiler, but also combines the advantages of a bug trapper and a tracer. With all these features working together, SpeedTrace provides the developer with a most powerful toolkit to combat software imperfections and tackle development issues. Besides, it doesn’t alter the internal timing of your dot.net applications, and therefore, doesn’t lead to mixed results or misleading conclusions.
We understand that developers always wish to be in perfect control of their work. With the SpeedTrace dot.net profiler and the help of its sophisticated trigger and filter system, developers will be able to control the entire profiling and tracing process of their dot.net applications during runtime.
Performance plays a crucial role wherever software development is involved. Adequate performance analyses and regular testing and evaluation will help developers to produce dot.net tools of supreme quality. And it goes without saying that quality creates customer satisfaction, and customer satisfaction … SALES!
There are lots of things you can’t start early enough — how about profiling the performance of your dot.net applications?
We hope we were able to arouse your curiosity and would like to invite you to take part in this new dot.net blog. Let’s generate completely fresh, new ideas together to help our dot.net developer colleagues brighten their daily routine!
dot.NET Profiler Blog by ipcas GmbH
Copyright 1988 - 2012 ipcas GmbH
ipcas GmbH is a member of Data Respons Group
