ASP.NET Performance Engineering - Stress Test Your Architecture, Design, And Code

--.net 性能调优

simhare — Thu, 04 Jun 2009 11:04:54 GMT

http://www.javaeye.com/news/3022-recommendation-25-to-help-you-net-application-performance-tuning-re...

Me estás eSTRESSando !!

Mario Cortés Flores — Mon, 08 Sep 2008 21:48:27 GMT

Es lo que me ha estado diciendo el servidor de pruebas. Esa semana la hemos dedicado a probar toda la

WCF Testing Tool(转)

菩提树下的杨过 — Thu, 04 Sep 2008 16:10:09 GMT

原文:http://jayce.clearviewtickets.info/wcftestingtool.html bestvideo:

ASP.NET Data Binding Performance – Collection Is More Expensive Than Datatable

Alik Levin's — Fri, 01 Aug 2008 14:41:03 GMT

In my previous post - Best ASP.NET Performance Winner For Data Binding - Hands Up To Response.Write()

ASP.NET Data Binding Performance – Collection Is More Expensive Than Datatable

Alik Levin's — Fri, 01 Aug 2008 14:19:58 GMT

    In my previous post -  Best ASP.NET Performance Winner For Data Binding - Hands

Best ASP.NET Performance Winner For Data Binding - Hands Up To Response.Write()

Alik Levin's — Thu, 31 Jul 2008 15:30:09 GMT

     To achieve best performance you need to make decisions based on trade-off between

Interesting Finds: 2008.05.06

gOODiDEA.NET — Tue, 06 May 2008 11:49:27 GMT

.NET A-Star Pathfinding in C# JIT Optimizations Creating portable ASP.NET applications that work on IIS

re: ASP.NET Performance Engineering - Stress Test Your Architecture, Design, And Code

Alik Levin — Tue, 06 May 2008 00:50:57 GMT

@Yossi

Thanks, partner!

@David

Good point! Knowing what you are optimizing is key! You must decide upfront - whether to write code fast or write code that is fast ;)

Sometimes you cannot (impossible) to optimize code that is written without performance in mind. Sometimes you need to redesign or even to rearchitect it... want to optimize on resources (time and money)? Build your app with perf in mind upfront

re: ASP.NET Performance Engineering - Stress Test Your Architecture, Design, And Code

David Groozman — Mon, 05 May 2008 22:44:12 GMT

In one hand - it is good to care about the performance all the time. But writing fast code is expensive. Fast code is more complicated and hard to maintain. Stored procedures are harder to write then code on C#. I would consider approach of writing maintainable code and optimize only when needed?

re: ASP.NET Performance Engineering - Stress Test Your Architecture, Design, And Code

Yossi Elkayam — Mon, 05 May 2008 20:16:06 GMT

Alik :) You're A Best Practicer , Thanks