I'm curious if anyone has made attempts to "cache" the bootstrap process in Drupal.

Normally, Drupal will run the 7 bootstrap phases on each request, but perhaps on a deployed production system, one could "do away" with some or all of these?

Possible suggestions I have in mind could be

1. Serializing the bootstrapped state and sticking it into memcache
2. A script could generate a patch for bootstrap.inc that will hardcode certain information into the file.
3. I believe chx has tried to keep a bootstrapped Drupal running on libevent.
4. Other craziness?

What attempts are there, and which are known to be (somewhat) reliable?

I'm curious if anyone has made attempts to "cache" the bootstrap process in Drupal.

Normally, Drupal will run the 7 bootstrap phases on each request, but perhaps on a deployed production system, one could "do away" with some or all of these?

Possible suggestions I have in mind could be

1. Serializing the bootstrapped state and sticking it into memcache
2. A script could generate a patch for bootstrap.inc that will hardcode certain information into the file.
3. I believe David Strauss has tried to keep a bootstrapped Drupal running on libevent.
4. Other craziness?

What attempts are there, and which are known to be (somewhat) reliable?

I'm curious if anyone has made attempts to "cache" the bootstrap process in Drupal.

Normally, Drupal will run the 7 bootstrap phases on each request, but perhaps on a deployed production system, one could "do away" with some or all of these?

Possible suggestions I have in mind could be

1. Serializing the bootstrapped state and sticking it into memcache
2. A script could generate a patch for bootstrap.inc that will hardcode certain information into the file.
3. I believe chx has tried to keep a bootstrapped Drupal running on libevent.
4. Other crazyness?

What attempts are there, and which are known to be (somewhat) reliable?

I'm curious if anyone has made attempts to "cache" the bootstrap process in Drupal.

Normally, Drupal will run the 7 bootstrap phases on each request, but perhaps on a deployed production system, one could "do away" with some or all of these?

Possible suggestions I have in mind could be

1. Serializing the bootstrapped state and sticking it into memcache
2. A script could generate a patch for bootstrap.inc that will hardcode certain information into the file.
3. I believe chx has tried to keep a bootstrapped Drupal running on libevent.
4. Other craziness?

What attempts are there, and which are known to be (somewhat) reliable?