Poor Javascript performance is an obstacle in AJAX development

I’m currently developing my first AJAX based web application. The goal is to have a pure AJAX application, i.e. never reload the entire page, use only background XMLHTTPRequest to contact the server.

My observations so far is that it is possible to do most of the application logic I need. But the performance of Javascript execution in the browser is a big obstacle. The application is centered around a list of data items in a scrollable area. The list is loaded as preformatted XHTML with an AJAX request and then some Javascript is used to decorate it with event handlers. I would like to display up to 1000 items at once, but I quickly realized that this wasn’t possible. The Javascript loop triggered the timeout in the browser after about five seconds. This timeout does not count waiting for the server to deliver the response, it only counts the client Javascript code to process the response. This timeout is reasonable, it’s clearly not acceptable for the user to wait over five seconds for the browser to process the server response (in addition to wait for the server and network to deliver the response). After limiting to 100 item, it works.

To make it feasible to build pure AJAX web applications working with lots of data, the performance of Javascript execution in the web browsers needs to improve drastically. In particular, iterating over large collections must be much faster. I think that a way to acheive this would be to use Just-in-time compilation of the Javascript code, similar to what modern JVM:s does.

The web browser I use is Mozilla Firefox in Linux.

This entry was posted in AJAX, web. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *



(this is a captcha)