Is there perfomance benefits of using asp.net mvc comparing to regular webforms with whole page life cycle, viewstate and all that? It seems to me that mvc view engine still uses page life cycle events which may slow things down. Do I gain perfomance replacing
default view engine with nVelocity, who doesn't have page events but uses custom programming language (few loop types, variable assignments, ...)?
Is there some benchmarks of ASP.NET MVC vs MonoRail (vs Promesh.net) in terms of req/sec?
While I haven't done any actual benchmarking, I would assume there are performance benefits simply because there is less "junk" emitted to the browser. No viewstate hash, no funky id's, etc... You get to control exactly what is sent to the browser.
Is there perfomance benefits of using asp.net mvc comparing to regular webforms with whole page life cycle, viewstate and all that? It seems to me that mvc view engine still uses page life cycle events which may slow things down.
There is a perf gain in that the whole PostBack mechanism is not part of the picture anymore, and the page is essentially a bunch of script commands. As ScottGu pointed out in his demo to Alt.NET (where he intro'd MVC), ASP.NET MVC can handle a tremendous
load.
Haven't done any testing with regards to the other engines - but it would be interesting :).
We have yet to do our own internal perf and stress measurements and optimizations. In fact, the task to build an app that exercises many of the features of MVC so that we can point our stress tester at it is on my plate.
Such an app would only be used internally for this testing. I could sure use some help with that. *hint* *hint*. ;)
Phil Haack (http://haacked.com/)
Senior Program Manager, Microsoft
I'm little afraid to start building my next web site with this version of mvc, mostly because documentation and possible bugs. Maybe guys from CastleProject (monorails) can do some testing? I read somewhere that they inserted nVelocity view engine - and
because it's very nice syntax and separation of concerns it would be great to compare it with aspx view engine. Somehow i think nvelocity with it's absent of code-behind file (page events) gain some perf points here.
Looking at mvc "tiers" (don't know how to call it), it's not problem to write good designed code in Model and Controller, but its link to View, and rendering View it interesting part. That would be nice to measure and stress test somehow.
hudo
Member
22 Points
48 Posts
Perfomance
Jan 07, 2008 09:17 AM|LINK
Is there perfomance benefits of using asp.net mvc comparing to regular webforms with whole page life cycle, viewstate and all that? It seems to me that mvc view engine still uses page life cycle events which may slow things down. Do I gain perfomance replacing default view engine with nVelocity, who doesn't have page events but uses custom programming language (few loop types, variable assignments, ...)?
Is there some benchmarks of ASP.NET MVC vs MonoRail (vs Promesh.net) in terms of req/sec?
Related discussion from promesh forum: http://www.forum.activa.be/viewtopic.php?f=6&t=117
mvc perfomance
Hear me tweetting
ChadThiele
Participant
983 Points
274 Posts
Re: Perfomance
Jan 07, 2008 02:22 PM|LINK
While I haven't done any actual benchmarking, I would assume there are performance benefits simply because there is less "junk" emitted to the browser. No viewstate hash, no funky id's, etc... You get to control exactly what is sent to the browser.
robconery
Participant
852 Points
195 Posts
Re: Perfomance
Jan 07, 2008 03:41 PM|LINK
There is a perf gain in that the whole PostBack mechanism is not part of the picture anymore, and the page is essentially a bunch of script commands. As ScottGu pointed out in his demo to Alt.NET (where he intro'd MVC), ASP.NET MVC can handle a tremendous load.
Haven't done any testing with regards to the other engines - but it would be interesting :).
Haacked
Contributor
6901 Points
412 Posts
Re: Perfomance
Jan 09, 2008 07:20 AM|LINK
We have yet to do our own internal perf and stress measurements and optimizations. In fact, the task to build an app that exercises many of the features of MVC so that we can point our stress tester at it is on my plate.
Such an app would only be used internally for this testing. I could sure use some help with that. *hint* *hint*. ;)
Senior Program Manager, Microsoft
What wouldn’t you do for a Klondike bar?
hudo
Member
22 Points
48 Posts
Re: Perfomance
Jan 09, 2008 07:49 AM|LINK
I'm little afraid to start building my next web site with this version of mvc, mostly because documentation and possible bugs. Maybe guys from CastleProject (monorails) can do some testing? I read somewhere that they inserted nVelocity view engine - and because it's very nice syntax and separation of concerns it would be great to compare it with aspx view engine. Somehow i think nvelocity with it's absent of code-behind file (page events) gain some perf points here.
Looking at mvc "tiers" (don't know how to call it), it's not problem to write good designed code in Model and Controller, but its link to View, and rendering View it interesting part. That would be nice to measure and stress test somehow.
keep a good work!
Hear me tweetting