[wp-trac] Re: [WordPress Trac] #7765: Parallel Processing

[WordPress Trac]

#7765: Parallel Processing
-------------------------+--------------------------------------------------
 Reporter:  dcole07      |        Owner:  anonymous
     Type:  enhancement  |       Status:  closed   
 Priority:  normal       |    Milestone:           
Component:  General      |      Version:           
 Severity:  normal       |   Resolution:  invalid  
 Keywords:               |  
-------------------------+--------------------------------------------------
Comment (by jacobsantos):

 Replying to [comment:2 Otto42]:
 > The wp-cron stuff is already being processed in parallel by making a hit
 to the wp-cron process via http and ignoring the result (because it just
 needs to start the thing, not care about what it does). Alternate methods
 are popen and pctrl_fork. Perhaps a generic parallel process spawning
 function to use one of the many methods available to spawn a separate
 process should be added to the code. As a fallback, it could simply run
 the code itself not in parallel if none of the methods worked.
 [[BR]]
 pctrl_fork() can not be used in the web SCGIs. Paranoid web hosts will
 most likely disable popen() since it handles shell commands. The current
 way the cron is handled is probably the most supported and best way to do
 it. Well, besides setting up a crontab job.

 I think the problem is whether you are talking about parallel as in
 pctrl_fork() or parallel as in how the current wp-cron is handled.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/7765#comment:3>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software