drcmg28484 2017-03-09 20:28
浏览 569

与通过Unix Socket和TCP / IP套接字运行PHP-FPM有什么区别?

There are these two ways of running PHP-FPM. I know that nothing is bullet-proof in tech, but what are the pros and cons from both methods?

  • 写回答

1条回答 默认 最新

  • dstbtam8732 2018-04-13 13:22

    The difference is mainly the added overhead of using the full network stack to "pack" and "unpack" every piece of data. Mind you that the overhead is negligible for most deployments

    • Using a socket (e.g. listen = '/tmp/php-fpm.sock') makes sense when both the front-end (e.g. Nginx) and php-fpm are in the same box and

      1. You have the option to scale horizontally both the front and back-end together (say you are building a container with both and you can create more containers, each with a working pair) or
      2. Your only option is to scale vertically the one "box" you are using (say, you add more CPU, RAM, etc)
    • Using a TCP connection (e.g. listen = makes sense if you want to de-couple the front and the back-end, for example, if you decide to scale up your environment by having a single Nginx receiving connections and passing the work via the network to a cluster of php-fpm boxes

    Every environment is different, so as always, the only true option is to start with the one setup that seems right, load-test, and keep measuring the performance so you can try different options as your load requirements evolve (normally, you go with the one that is cheaper to implement or easier to maintain, since both are solid, battle-tested approaches)

    本回答被题主选为最佳回答 , 对您是否有帮助呢?



  • ¥60 补全networkx TODO部分。
  • ¥15 有内推吗,云计算linux运维方向
  • ¥30 sort cuteSV.vcf by bcftools用IGV可视化出现报错
  • ¥100 SOS!对STK中导出的天体图像进行质心提取有没有人做过啊
  • ¥15 python 欧式距离
  • ¥15 运行qteasy报错
  • ¥15 遗传算法解决有工序顺序约束的大规模FJSP问题
  • ¥15 企业消防水炮塔设计方案
  • ¥20 WORKBENCH网格划分
  • ¥60 急招师兄远程解决下载NPCAP的BUG!