Friday, November 30. 2007
dot.NET Profiler = Performance. Make a noise!
A dot.NET profiler provides you with the ability to time areas of an application, normally an entire application, so that bottlenecks can be discovered and displayed. Hence, the buzz practice of profiling which means during-runtime performance monitoring of programs developed in dot.NET.
When developing dot.net applications, it is always necessary to take the performance factor into account right from the outset. That is how you can save a lot of costs for rewriting modules, modifying codes, or deploying the same application over and over again.
Developers know as a fact that in order to write good quality codes, it is necessary to make frequent code reviews, testing different ways of implementing them to determine their performance impact on dot.net applications. However, these kind of reviews tend to be slow-going and tedious, thus exponentially increasing development time and sometimes developers’ frustration while organisations face the dual task of having to create software that meets best practice standards and, at the same time, deliver dot.net applications within the set budget on time.
This is where SpeedTrace dot.net profiler enters the scene and hooks into dot.net applications by scrutinizing calls (enter/exits), JIT compilations, managed and unmanaged code transitions, thread switches, garbage collection, exception handling, data traces, and more ... all during program execution — consequently making developers' lives easier.
There are many dot.net profilers on the market, but not many like SpeedTrace robust enough to work the load of large-scale applications. Dot.net applications tend to grow in complexity, therefore, companies are struggling hard to fulfil the necessary levels of application performance. This applies especially when applications running on multi-core systems are managed and profiled improperly and thus impair the organisation's ability to meet the performance demands of complex applications.
Software quality is closely related to flawless operability which is translated into faultless performance applications. In most cases the failure to use adequate dot.net profiler tools able to quickly provide both accurate and relevant information leads to poor software quality. Therefore, it is important to spend sufficient time and care on performance issues within dot.NET applications since this is what, in the end, will reward you with the most customer satisfaction and business success.
Monday, November 26. 2007
dot.Net Framework 3.5 Released!
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.
Friday, November 23. 2007
SpeedTrace dot.Net Profiler 3.2.14 Released
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.
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.
Wednesday, November 21. 2007
The dot.Net Prio conference


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.
Friday, November 16. 2007
Dot.Net Profiler and Tracer in one!
Bug-trapping and dot.net analysis can be a very time-consuming task ... See how you can improve it!
Continue reading "Dot.Net Profiler and Tracer in one!"
(Page 1 of 2, totaling 6 entries)
» next page


