I’d like to tap from your experience on how to continue scaling our hardware. Here’s our corner stone data: 2.2 Million posts currently growing ~80k per month 35k users, growing ~1.5k per month We’re now running on a Hetzner VM with 8 exclusive cores and 32G of RAM. We started to see limitations…

Why are you looking to scale? Are your API response time metrics degrading? [이미지] helmi: we’re nearing a 100% server utilization limit. What resource are you refering here? CPU? Disk space? Memory?

How many page views are you having? [이미지] helmi: db_shared_buffers to 8192MB Ignore all the advice you find on the internet and set it to 40-50% of your memory. Can you share some sar output?

[이미지] Falco: Why are you looking to scale? Because I’m planning ahead. We might not need to scale right now but looking at the growth we see and the growing need of resources we saw in the past I’m just planning ahead right now to think about possible next steps. [이미지] Falco: What resour…

[이미지] helmi: Mainly CPU - after todays update we’re coming back from Load ~8-9 on peak hours to what it seems like ~6ish now. You will want to investigate what exactly is using that CPU. It can be: Unicorn web workers PostgreSQL Sidekiq, like image optimization background jobs Redis nginx (…

Looking at CPU time I’d say it’s mainly unicorn workers: [Screenshot 2022-01-26 @ 21.30.36@2x]

Maybe ditch the dedicated CPU thing and use this offering here? [image] Sounds like something more appropriate for your needs.

I was thinking about that option already. We used the non dedicated CPUs earlier and the “upgrade” to dedicated ones didn’t move us forward a whole lot.

I’m not sure if CPU is your bottleneck. Do you have some sar output to share in the meanwhile?

Yes, I do, but not really peak hours yet. Will have those by tomorrow. CPU usage is definitely reduced sinced I raised worker connections yesterday - not sure how much though. 12:00:01 AM CPU %user %nice %system %iowait %steal %idle 08:45:01 AM all 40.22 2.21 …

What would be some useful sar stats to consider?

더 큰 규모로 확장하기 (200만+ 게시글, 월 8만+ 건)

제품 지원 자체 호스팅

helmi (Helmi) 1월 26, 2022, 8:33오후 7

CPU 시간을 살펴보면, 주로 유니콘(unicorn) 워커들이 원인인 것 같습니다:

글		댓글	조회수
I just hit my CPU cap on the Digital Ocean 2GB/2xCPU plan Self-hosting hosting	35	18041	4월 30, 2018
Discourse installation has been getting slower and slower and slower Self-hosting server-resources	36	2165	4월 15, 2023
Discourse overloaded real traffic or DDOS? 100% CPU usage despite of decent traffic and high specs server Self-hosting server-resources	18	2652	9월 25, 2021
Our discourse overload because of a custom plugin. Please help me Self-hosting hosting	46	2630	8월 22, 2022
My discourse speed is very slow Self-hosting	24	5412	3월 4, 2021

더 큰 규모로 확장하기 (200만+ 게시글, 월 8만+ 건)

Related topics