I'm interested in using Spark for an open source pet project of mine that runs with the asp.net mvc framework. I wonder if anyone has real experience with it and knows how it performs compared to the normal asp.net view engine?
I know that marketwatch.com runs asp.net mvc and Spark.
At this point there are two engines inside of the view engine collection: the Web forms view engine (the default ASP.NET MVC view engine) and the Spark View Engine.
Spark is a view engine for ASP.NET MVC and Castle Project MonoRail frameworks. The idea is to allow the html to dominate the flow and any code to fit seamlessly.
View Engine is responsible for rendering the view into html form to the browser. By default, Asp.net MVC support Web Form(ASPX) and Razor View Engine. There are many third party view engines (like Spark, Nhaml etc.) that are also available for Asp.net MVC.
The view templates are parsed to generate and compile a class that does nothing more than write output. After the first request of a view there's no real work being done other than to create an instance of that type and render.
It's been profiled for cpu and memory costing pretty extensively. I believe it's safe to assume there's nothing measurably slower in Spark - and in general it's unlikely the rendering in either Spark or WebForms view engines would be a bottleneck in a real-world application.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With