blocks|key|2044204|text|您的计划应该是可行的，但是我认为您可以通过使用PHP过程控制函数来避免所有的数据库通信甚至轮询。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2044205|将主进程分叉的次数与需要它并行运行的任务一样多。请参阅：分叉|ordered-list-item|2044206|在这些分叉过程中执行任务，并让它们正常退出。|2044207|启动这些任务的进程应该在SIGCHLD信号退出时监听SIGCHLD信号，等待它们全部完成。或者，如果他们没有在您选择的超时之前，然后发送SIGTERM信号给他们清理。见：西格托和杀掉。|2044208|但是，您必须在PHP脚本中使用这些函数，因为.|2044209|http://www.php.net/manual/en/intro.pcntl.php|2044210|不应在web服务器环境中启用过程控制，如果在web服务器环境中使用任何过程控制功能，则可能会发生意外结果。|blockquote|2044211|但是您的web服务器可以轻松地exec()您的CLI脚本，这将完成所有的艰苦工作，返回这些任务的状态，等等。|style|CODE|2044212|entityMap|0|LINK|mutability|MUTABLE|url|http://www.php.net/manual/en/book.pcntl.php|1|http://www.php.net/manual/en/function.pcntl-fork.php|2|http://www.php.net/manual/en/function.pcntl-sigtimedwait.php|3|http://www.php.net/manual/en/function.posix-kill.php|4^0|N|9|0|0|S|2|1|0|0|2D|3|2|2H|2|3|0|0|0|18|4|0|0|F|6|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@$A|1B|B|1C|1|1D]]|C|$]]|$1|D|3|E|5|F|7|1E|8|@]|9|@$A|1F|B|1G|1|1H]]|C|$]]|$1|G|3|H|5|F|7|1I|8|@]|9|@]|C|$]]|$1|I|3|J|5|F|7|1J|8|@]|9|@$A|1K|B|1L|1|1M]|$A|1N|B|1O|1|1P]]|C|$]]|$1|K|3|L|5|6|7|1Q|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|1R|8|@]|9|@$A|1S|B|1T|1|1U]]|C|$]]|$1|O|3|P|5|Q|7|1V|8|@]|9|@]|C|$]]|$1|R|3|S|5|6|7|1W|8|@$A|1X|B|1Y|T|U]]|9|@]|C|$]]|$1|V|3|-4|5|6|7|1Z|8|@]|9|@]|C|$]]]|W|$X|$5|Y|Z|10|C|$11|12]]|13|$5|Y|Z|10|C|$11|14]]|15|$5|Y|Z|10|C|$11|16]]|17|$5|Y|Z|10|C|$11|18]]|19|$5|Y|Z|10|C|$11|N]]]]

Your plan should work, but I think you could avoid all the database communication and even polling by using the <a href="http://www.php.net/manual/en/book.pcntl.php" rel="nofollow">PHP Process Control functions</a>.

<ol>
<li>Fork your main process as many times as tasks you need it to run in parallel. See: <a href="http://www.php.net/manual/en/function.pcntl-fork.php" rel="nofollow">pcntl_fork</a></li>
<li>Perform your tasks in those forked processes and let them exit normally.</li>
<li>The process that initiates the tasks should wait for them to all complete by listening for their SIGCHLD signals as they exit. Or if they don't before your chosen timeout, then send the SIGTERM signal to them to clean up. See: <a href="http://www.php.net/manual/en/function.pcntl-sigtimedwait.php" rel="nofollow">pcntl_sigtimedwait</a> and <a href="http://www.php.net/manual/en/function.posix-kill.php" rel="nofollow">posix_kill</a>.</li>
</ol>

You will have to use these functions in a PHP CLI script, though, because...

<a href="http://www.php.net/manual/en/intro.pcntl.php" rel="nofollow">http://www.php.net/manual/en/intro.pcntl.php</a>

<blockquote>
 Process Control should not be enabled within a web server environment
 and unexpected results may happen if any Process Control functions are
 used within a web server environment.
</blockquote>

But your web server could easily <code>exec()</code> your CLI script, which will do all the hard work, return the status of those tasks, etc.

blocks|key|1014306|text|如果您的外部调用只是HTTP请求，则可以使用curl并执行多个请求。他们似乎完全满足了你的需要。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1014307|如果情况不一样，我可以强烈推荐吉尔曼。|offset|length|1014308|如果您想弄脏您的手并编写您自己的守护进程，我建议跳过IPC函数，进行一些更高级别的操作，比如ZeroMQ，如果它们死了，也许可以使用监督员d重新启动它们。编写长期运行的PHP进程相对比较困难，因此您必须在构建过程时考虑到外部脚本将随机死掉，并准备优雅地处理它。|1014309|entityMap|0|LINK|mutability|MUTABLE|url|http://gearman.org/|1|http://www.zeromq.org/|2|http://supervisord.org/^0|0|F|3|0|0|1A|6|1|1U|4|2|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@$D|V|E|W|1|X]]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@$D|Z|E|10|1|11]|$D|12|E|13|1|14]]|A|$]]|$1|H|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]|R|$5|K|L|M|A|$N|S]]]]

If your external calls are simply HTTP requests, you could simply use curl and do multiple requests. They seem to do exactly what you need.

If it's something different, I can highly recommend <a href="http://gearman.org/" rel="nofollow">Gearman</a>.

If you want to get your hands dirty and write your own daemon, I would suggest skipping the IPC functions, and go for something a bit more high-level, such as <a href="http://www.zeromq.org/" rel="nofollow">ZeroMQ</a>, and perhaps use <a href="http://supervisord.org/" rel="nofollow">Supervisord</a> to restart the PHP processes if they die. It's relatively hard to write long-running PHP processes, so you have to build this with the notion in place that the external scripts will die randomly and prepare to handle that gracefully.

I'm familiar with php-resque and other job-processing systems for handling background jobs, but I don't think it'll do what I need.

In this case, I have an incoming web service request that needs to perform multiple (2-4) independent callouts to external systems and return with a consolidated response to the client. Each callout might take 300-500ms, so I want each callout to be performed in parallel so that the entire process takes no more than 500ms+/- total.

my problem with php-resque and other systems is that waiting even 1 second to start issuing those callouts is too long to wait, and I'm considering another approach.

What I'm thinking:

<ol>
<li>each individual callout is described and stored in a database with a given unique request ID</li>
<li>we kick off the jobs immediately as a asynchronous php process (aka "worker process")</li>
<li>Each worker writes its result back to the job record and indicates that it's complete</li>
<li>meanwhile, we poll the job table every 50-100ms to check on the status of each job</li>
<li>when each is complete, we parse the results as necessary and return the response.</li>
</ol>

Of course, we'd implement a timeout for each request and the overall process...

Thoughts? Am I wrong? Could php-resque kick off multiple jobs in parallel virtually instantly?

Using a distributed processing system for FOREGROUND requests in PHP

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我熟悉php-resque和其他用于处理后台作业的作业处理系统，但我认为它不能满足我的需要。在这种情况下，我有一个传入的web服务请求，它需要对外部系统执行多个(2-4)独立的呼叫，并向客户端返回一个统一的响应。每个标注可能需要300-500 no，所以我希望每个标注并行执行，这样整个过程不需要超过500 no+/-总...

问在PHP中使用前台请求的分布式处理系统
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在PHP中使用前台请求的分布式处理系统EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在PHP中使用前台请求的分布式处理系统
EN