The queuing means you can do with more web workers
Additionally your median times look pretty high, can you get this on a faster CPU?
The queuing means you can do with more web workers
Additionally your median times look pretty high, can you get this on a faster CPU?
Unfortunately, even if the reason for the slowness is this plugin, I must say that this plugin is one of the main plugins of our community and can not be removed from us in any way, and users become heavily depended on it! ![]()
We currently use 24 web workers. Our Discourse is installed on a VM with 24 CPU cores with 2 GHz processing power and 24 GB of RAM. Unfortunately, it is not possible to change the main server now, unless we have no other way to improve performance.
Do you think that in the current situation, increasing the number of web workers can help to improve performance?
More web workers may reduce the queueing
You are trying to eliminate the orange lines from the active web request graph
Performance though will not get any better for your typical median request
Thanks, I understand now. So by looking at the graphs we can see if the number of web workers is enough or not enough for the system.
But according to you, to improve the speed and performance, we now need higher processing power and changing the parameters will not help more.
Be sure to test this at the earliest opportunity and inform the result.
502 错误是什么原因?是 unicorn 工作进程不足吗?我们刚迁移了服务器,用户在迁移后偶尔会报告 502 错误。我们有一个 6 核/16GB 的服务器,将 unicorn_workers 设置为 16(迁移服务器之前是 12),db_shared_buffer 设置为 4GB,db_work_mem 设置为 60MB。
过多的 unicorn 工作进程是否会导致 502 错误?(推测,因为在服务器迁移之前我们有 4 个更少的工作进程)
我正在尝试确定是需要调整配置还是需要解决其他问题。
谢谢。
是的,这似乎很高。将您的 unicorn workers 设置在每核 1 到 2 之间。
对于 6 核,不应超过 12。考虑到您相当大的共享缓冲区和我凭直觉的判断,我会将此设置在 10 左右,以匹配此类服务器规格。