Posted by mikeytown2 on February 12, 2012 at 11:27am
The HTTP Parallel Request Library module COULD be used to make Multi process Drupal happen via http://drupal.org/project/esi. I think all that is needed are some minor changes to the ESI module so it will issue non blocking requests to the ESI fragments URLs and we have parallel page rendering.
Questions? What did I miss? Why is this a bad idea? etc..
Comments
While that is a good idea, I
While that is a good idea, I am worried a little about bootstrap times.
In that case I would love to see a combination with gearman job server, which is holding several Drupal instances open for such requests.
I build a prototype a while ago and while views had some memleaks at that time, it did work really well for ajax views.
That way you would not have n requests for n blocks, but rather for example 4 drupal instances, where each is satisfying n/4 blocks.
Best Wishes,
Fabian
Reading up on Gearman, how
Reading up on Gearman, how would you use Drupal in a suspended state "waiting" for requests? It would seem that it requires an always-running server (like node.js) rather than a per-request process like Drupal.
I did this on D6 a while back
I did this on D6 a while back and it wasn't perfect by any means but I just had a copy of index.php looping waiting for events from gearmand in the standard way. Each event that was passed to the client worker had to include lots of environment stuff like the $_GET, $_POST, $user e.t.c. and that stuff needs to be torn down after each request.
You'll probably run into problems with static caches like in node_load which need to get added to your list of things to tear down after each request to the client.
Full Fat Things ( http://fullfatthings.com ), my Drupal consultancy that makes sites fast.