PUBLIC MARKS with tags .net & performance

In .NET, there are several ways to extract data from a data source. The two most common techniques using ADO.NET involve the use of the DataReader or the filling of a DataSet or DataTable with a DataAdapter. In this article, a very easy-to-reproduce set of tests is analyzed to determine which techniques performs the fastest. Further, additional variables such as N-Tier architecture and the effects of caching on the results are considered. Finally, I recommend some best practices based on the results

good stuff for perfmon

This article provides a high-level performance comparison between Windows Communication Foundation (WCF) and existing Microsoft .NET distributed communication technologies.

Identify performance bottlenecks quickly and easily Optimize memory usage and locate memory leaks Visual Studio integration with context sensitivity Download file includes FREE PInvoke.net Visual Studio Add-in

To summarize the results, WCF is 25%—50% faster than ASP.NET Web Services, and approximately 25% faster than .NET Remoting. [...] in one case WCF is nearly 100% faster but in another scenario it is nearly 25% slower.

Un blog sur le développement informatique, l'algorithmique avancée et la finance de marché (Risk Management, suivi de la performance...)

.net 性能测试小工具

Nutshell: .NET 2.0 was 10x faster than .NET 1.1. MSXML6 was 15% slower than MSXML4.

Compare and contrast performance characteristics of real-life ASP.NET Web services, .NET Enterprise Services components, and .NET Remoting components, and get recommendations on how to best use these technologies.