OutPost: Performance Tuning and Optimization

Wednesday, October 12, 2005

The same principles for Performance Tuning and Optimization apply when developing with OutPost. You optimize by taking advantage of the view-state, page level caching, page fragment caching, application caching, session caching and the web server Cache.

With OutPost you can actually get further performance improvements:
- Splitting up your page and having more web forms on the same page, like in "The iGoogle Demo", is a great idea.
- Finding the balance of when to use the view-state and when not to is also important and would often require you to test your application and analyze the load times to find the right settings.
- Setting the IDs of the HTML elements that frequently get updated is a good idea, because OutPost compares the innerHTML of elements with IDs.

I'll grant you that AJAX is much nicer to the server. But I would say that OutPost is much nicer to the developer

I like the simple structure of ASP.NET Web Forms and the way that you can develop ASP.NET controls for different browsers (with or without DHTML, depending on the capabilities of the browser).

The improvements to ASP.NET in upcoming versions (e.g. the view-state) will also have impact on the performance in OutPost web applications.

The improvements that you mention in ASP.NET 2.0 that you can write asynchronous pages will also work in combination with OutPost.

ATLAS will also work in combination with OutPost to provide extra RIA features to up-level browsers.


Post a Comment

<< Home