For the past year I’ve talked about a tool coming from Microsoft called Doloto. Doloto is an optimization tool for AJAX applications. Doloto makes AJAX applications run faster by stubbing out unnecessary code so that the application can start fast, and then downloading the necessary code on-demand if it is actually needed. This way application execution and code download is interleaved. It also means that with Doloto, rarely used code is rarely downloaded. I’m not sure if this could really apply to our code base, but it’s worth taking a look and evaluating.
According to this blog Doloto does the following:
- Profiling information is used to calculate code coverage and a clustering strategy. This determines which functions are stubbed out and which are not and groups functions into batches which are downloaded together, called clusters.
First, I want someone to get a better understanding about what exactly Doloto is. Second, I would love for someone to play around with it, set it up and design a few experiments that make use of it. It could be that we find out very quickly that our application will struggle to work inside of a Doloto proxy and subsequently fail to leverage the advice coming from the profile.