So all the claims that the UNICORN WORKER should be 2*vCPU are wrong? My server is Intel Xeon E5-2686 v4 @ 2.30GHz—24vCPU+32GB Ram How many UNICORN WORKER do I need to set up? 8? or 48? My site have more than 7k users and about 1k daily engaged users. users sending 3k-7k posts per day. our commu…

That depends on a lot of factors. Like how big your database size is in comparison to your RAM, the ratio of logged-in to anonymous traffic, whether you have plugins that keep your Sidekiq queue busier, if you are running YJIT, etc. What is simple is looking at the MiniProfiler data during your pea…

Is there a simple human-friendly description of what Unicorn workers are doing? The impression I get is that every user page request has to go to a Unicorn worker to be dealt with. If you don’t have enough, the user has to wait. If you have too many… well maybe that costs you a little RAM?

[이미지] Ed_S: Is there a simple human-friendly description of what Unicorn workers are doing? They’re the application web servers.

It’s not peak now, but I think there’s a problem with the loading time. <a class="lightbox" href="https://global.discourse-cdn.com/meta/original/4X/2/a/d/2ad0e6159f2490b1f3871d63121f87d4307b9a64.png" data-download-href="/uploads/short-url/66LCgUO5NPnjkUrciEXNWOzvPM0.png?dl=1" title="The image shows a performance monitoring graph in a rendering application, with various timings for different tasks including GET request, rendering operations, and SQL queries, indicating a total query time of 1500.5 milliseconds and a response duration of 62 milliseconds. (由 AI 生成标题)" rel="noopener nofollow ugc">[The image shows a performance monitoring graph in a rendering application, with various timings for different tasks including GET request, rendering operations, and SQL queries, indicating a total query time of 1500.5 millise…

Looks like your 10 years old CPU is showing it’s age. Increasing Unicorn workers will allow you to serve more users simultaneously but won’t make an individual request any faster. Can you try enabling YJIT? [이미지] Running Ruby 3.2's YJIT in Production at Discourse Discourse Self-Hosters For thos…

[이미지] Editor0732: I think there’s a problem with the loading time With your hardware I would expect to get a mean logged-in list/latest time of around 150ms app, 80ms SQL. I’d start with 12 workers and see how it behaves with that. The best thing you can do is track metrics; if you want to k…

<a class="lightbox" href="https://global.discourse-cdn.com/meta/original/4X/d/b/1/db1babce536d92db4a793d4966a60c9dfa062d1f.png" data-download-href="/uploads/short-url/vgjQLItSNmyp5fOd3gCyg5lhaID.png?dl=1" title="The image displays a series of performance metrics for two pages over a period from 21:15 to 23:45, showcasing median and 98th percentile page performance, total example count, successful HTTP requests, and error rates with redirects. (由 AI 生成标题)" rel="noopener nofollow ugc">[The image displays a series of performance metrics for two pages over a period from 21:15 to 23:45, showcasing median and 98th percentile page performance, total example count, successful HTTP requests, and error rates with redirects. (由 AI 生成标题)] <a class="lightbox" href="https://global.discourse-cdn.com/meta/original/4X/9/5/9/959754947bdb599df7408e0bb543fb4aa85c15fb.png" data-download-href="/uploads/short-url/lllmKBI5JMAsGcitWKqKfHZXOIP.png?dl=1" title="The image shows various graphs and metrics related to server and container performance, including page views per second, active web requests, object allocation rate, Ruby heap stats, and container CPU and memory usage, along with sections indicating no data for CPU usage and memory usage. (由 AI 生成标题)" rel="noopener nofollow ugc">[The image shows various graphs and metrics relat…

[이미지] Falco: Looks like your 10 years old CPU is showing it’s age. :laughing: (/stops laughing, logs into hosting provider … ) [이미지] Falco: Can you try enabling YJIT? wow, is this not the default by now?? edit: ah of course you might have built with an old app.yml and not updated sin…

[이미지] merefield: wow, is this not the default by now?? It is in our hosting, but it is kinda hard to make it a default as people may be running in RAM constrained scenarions… That said, our JS build use so much more RAM than Discourse itself, that you may say that anyone that can build the J…

In these pictures, how many workers do you have setup? I’d say you should Increase workers a little, as you get a little queueing Enable YJIT, as your web time is quite slow

워커 수 권장: 코어 × 2?

제품 지원 자체 호스팅

Falco (Falco) 4월 25, 2025, 6:24오후 14

이 사진들을 보면 워커를 몇 개로 설정해 두셨나요?

저라면 이렇게 하겠습니다.

약간의 큐잉(대기열)이 발생하므로 워커 수를 조금 늘리세요.
웹 처리 시간이 꽤 느리므로 YJIT를 활성화하세요.

글		댓글	조회수
High CPU usage (Ruby) Product Support server-resources	20	1090	2월 3, 2025
How to avoid upstream timeouts? Product Support	24	9694	2월 25, 2019
Optimizing the number of Unicorns and buffer size Self-hosting server-resources	22	7157	6월 9, 2018
Best configurations for speeding up standalone discourse Self-hosting server-resources	25	4684	2월 14, 2024
Due to extreme load, this is temporarily being shown to everyone... when it's not really the case Self-hosting server-resources	19	2015	7월 21, 2023

워커 수 권장: 코어 × 2?

Related topics