客运服务器升级：处理器 (CPU) 内核 VS RAM？
我浏览了 Passenger 的文档，以了解它可以在硬件配置方面运行多少个应用程序实例。文档仅讨论 RAM
最佳值取决于系统的硬件和服务器的平均负载。您应该尝试不同的值。但一般来说，该值应至少等于您拥有的 CPU（或 CPU 核心）数量。如果您的系统有 2 GB RAM，那么我们建议值为 30。如果您的系统是虚拟专用服务器 (VPS)，并且有大约 256 MB RAM，并且还运行 MySQL 等其他服务，那么我们建议值为共 2 个。
它表示最小值可以是我们拥有的 CPU/CPU 核心数。我有一个带有一个 VCPU 和一个 VPS 的 VPS。 1GB 内存和我的服务提供商可以选择仅升级 RAM。我想知道我可以只升级 RAM 到什么程度？升级CPU数量有多重要？
I went through documentation of Passenger to find out how many application instances it can run with respect to hardware configuration. Documentation only talks about RAM
The optimal value depends on your system’s hardware and the server’s average load. You should experiment with different values. But generally speaking, the value should be at least equal to the number of CPUs (or CPU cores) that you have. If your system has 2 GB of RAM, then we recommend a value of 30. If your system is a Virtual Private Server (VPS) and has about 256 MB RAM, and is also running other services such as MySQL, then we recommend a value of 2.
It says minimum value can be number of CPU/CPU Cores we have. I have a VPS with one VCPU & 1GB RAM & my service provider has an option to just upgrade the RAM. I'm wondering how far I can just keep upgrading only RAM? How important it is to upgrade number of CPUs?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
快速回答
取决于哪些资源是您的应用程序的瓶颈。
长答案
您需要考虑一些因素：
可能还有其他因素需要考虑，但您的瓶颈可能是上述之一。如果 RAM 是您的主要瓶颈，请务必使用新可用的 RAM。但是，如果事实证明您的应用程序因 CPU 可用性或 IO 泛滥而变慢，那么再多的 RAM 也无法加快速度。
关于CPU核心的话题；我的理解是，运行 Passenger 的主 Apache 进程是一个单线程进程。 Apache 生成新线程来根据需要处理并发。理论上，每个额外的 CPU 核心都允许您生成
x*n个线程，其中x是您可以在单个 CPU 核心下最佳运行的线程数，而n< /code> 是 Apache 可用的 CPU 核心数。免责声明：我对 Passenger 内部结构了解不多；尽管这种逻辑通常适用于其他类型的 Apache 配置。
Quick Answer
Depends on what resources are the bottleneck for your app.
Long answer
You'll need to factor in a few things:
There can be other things to factor in, but your bottlenecks will probably be one of the above. If RAM is your main bottleneck, by all means use your newly available RAM. However, if it turns out that your app is being slowed down by CPU availability or flooded IO, no amount of RAM is going to speed things up.
On the topic of CPU cores; my understanding is that the main Apache process that runs Passenger is a single threaded process. Apache spawns new threads to handle concurrency on an as-needed basis. Each additional CPU core theoretically allows you to spawn
x*nthreads, wherexis the number of threads you can optimally run under a single CPU core andnis the number of CPU cores available to Apache.Disclaimer: I'm not very well read on Passenger internals; though this logic usually holds true for other kinds of Apache configurations.