우리의 커뮤니티는 실제 세계의 이벤트에 따라 트래픽이 급증합니다. 정확히 말하면 아이스하키 경기로, 약 2.5~3시간 동안 특정 토픽에 1,000개의 메시지가 몰리는 상황이 발생합니다. 다른 토픽에서 논의되었듯이, 이러한 트래픽 급증을 처리하는 데 어려움을 겪고 있습니다.
이로 인해 제한된 예산 내에서 다른 호스팅 옵션을 탐색하게 되었습니다. 목표 예산은 월 50유로 정도입니다. 이전에 제안을 조사한 이후로 시장은 많이 변했습니다.
Hetzner에서는 단 42유로에 Ryzen 5 3600 CPU가 탑재된 전용 서버를 구할 수 있습니다. 6코어를 갖춘 상당히 강력한 CPU입니다. 마침 이 노트북에도 비슷한 CPU가 탑재되어 있는데, 일반적인 성능이 좋은 VPS보다 싱글스레드 처리 성능이 약 40~50% 더 빠릅니다.
하지만 같은 가격대에서는 코어 수가 훨씬 많지만 성능이 다소 낮은 VPS를 구매할 수도 있습니다. Contabo는 단 27달러에 10코어를 제공하며, Hetzner는 62유로에 최대 16코어를 제공합니다. 이 외에도 수많은 다른 제공업체가 있습니다.
이러한 제안들을 보며, Discourse의 피크 출력 극대화를 위해 어떤 코어 구성이 이상적인지 궁금해졌습니다. 성능이 높은 소수의 코어일까요, 아니면 많은 수의 코어일까요?
이를 검색해 보았지만 대부분 제가 이전에 작성한 게시글들을 발견했습니다 초기에 간간이 논의되었던 주제이지만, 최근에는 충분히 논의되지 않은 것 같습니다. 수년에 걸쳐 코드가 많이 변경되었으므로, 소프트웨어의 동작 방식이나 일반적인 권장 사항도 변했을 수 있습니다.
You’re right it’s old posts but the trend seems consistent
How about a scalable instance for the game nights ? With a little down time it’s easy to backup and spin larger or smaller. I had a similar problem with a jitsi instance (great component BTW ) , most of the time it sat on its hands, but few times a week…
Even though I introduced our case in the OP, the intention was to discuss this on the generic level. I may be on the hosting market in the mid-term future, regardless whether I have our root case identified or not.
For Discourse, you should favor fast cores over more cores. If you can get both, that’s even better (for load scenarios). But in the typical case, 2 fast cores will do better overall than 4 slow cores.
We tend to measure this in build time, here are some examples. But any single threaded benchmark will also do.
Ideally you want a build time under 4 minutes (240 seconds).
I’m no expert on the subject, but I’m not sure the virtual cores of a VPS are comparable at all to physical cores of a CPU. I guess that to have a broad approximation, you could look at the amount of RAM offered, and assume they run these VPS on a 256 Mo computer. Contabo with their “10 (virtual) cores” offers 60 Mo of RAM. They probably run 4 of these on something approx. equivalent to the Hetzner dedicated server you mention (a server with 256 Mo). So, I would assume the “10 (virtual) cores” are approx a quarter of the performance of the “6 (physical) cores”. Let’s say half tops if they run 2 of them on a 128 Mo computer (which may have a better or slower CPU than the Hetzner machine, who knows).
(You can really only compare “virtual cores” between the different VPS offers of the same provider. I’m not even sure it makes sense for comparisons of VPSes of different providers).
If you want to know for sure, you have to subscribe for 1 month and run a benchmark. Or convince them to run it for you, or offer you a free trial for a short period of time. If it’s really performance you’re after, that’s the real only way to know for VPSes. Or go with a dedicated server where you have more accurate informations.
EDIT: VPS providers like Contabo usually use KVM to do virtualization, and after a search, it indeed seems you can show more “virtual cores” than you actually have physical cores. Example:
As I was looking at this offer; and thinking hum good deal, I saw that the RAM wasn’t ECC, so quick search on the web, and what pops up ? this blog article by Jeff
The video of the CPUs made my day…
Oh wow, I’m already hosting with Hetzner but at a higher price point with a slower CPU & less storage than their current Ryzen boxes. This makes it very interesting to switch… thanks for the note!
Has anybody done some tests with different CPUs regarding the size of L3 cache?
I’ve seen some mentions that Ruby is very demanding for memory. That could give a hint about possible impact of CPU cache size, because Discourse works with large datasets.
I’m deciding on new server and choosing the right CPU. I wonder whether to go with highest clock or take into account also L3 cache size..
Currently I’m looking at Intel® Xeon® E-2174G with 4 cores clocking 3,8GHz and 8MB cache. But there are more expensive options with 12MB or 16MB cache. Are they worth the money?
초기에 간간이 논의되었던 주제이지만, 최근에는 충분히 논의되지 않은 것 같습니다. 수년에 걸쳐 코드가 많이 변경되었으므로, 소프트웨어의 동작 방식이나 일반적인 권장 사항도 변했을 수 있습니다.
) , most of the time it sat on its hands, but few times a week…
hum good deal, I saw that the RAM wasn’t ECC, so quick search on the web, and what pops up ? 