[MTOS-dev] MT-Search throttling

[Byrne Reese]

>>  The sequence diagram is hard to do in ASCII, but it would look like this:
>> 
>>  1. request received
>>  2. check load average
>>  3. bootstrap app
>>  4. process comment/search/trackback
>>  5. return result
> 
> Right.  It may be time for us to redesign and elaborate the
> bootstrapper, in order to make it easier to add pre-post handlers as
> you mentioned above and support Reed-san's dispatcher ;-)

This is very interesting.

One challenge before us is that the app context is loaded all at once, and
it is huge. But currently it is necessary because it contains all of the
configuration info etc.

We need a progressive loader. So now the call stack looks like this:

1. request received
2. initialize context with config data and plugin meta data (memory
footprint: n)
3. fire pre_init callbacks (pass in existing app context)
4. bootstrap rest of app
5. process request
6. return result

The question in my mind is, "what is the bare minimum we can load in step
#2?"

Byrne