TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Automated Scalability with Python on nginx

45 点作者 mahipal将近 15 年前

3 条评论

rythie将近 15 年前
I thought this guy was being sarcastic the first time I read it. If he is serious, there are so many problems with it.<p>- Getting 823 requests/second should more than achievable with one server and memcache. Nginx can serve over 2000 requests/second in a single process on a single machine in 10Mb or so of memory.<p>- his benchmark only tests one page, the first one (with 10 posts on it)<p>- Cassandra is designed for high write bandwidth, which typically wouldn't be a single author blog using an external commenting system
agazso将近 15 年前
It is so wrong on many levels I don't even know where to start. He is scaling a blog engine (!) with a "scalability daemon" instead of generating html pages and storing them in cache. He could then serve ten thousands of pages with one server instead of 823 request of seconds and the complex setup.
评论 #1432081 未加载
评论 #1432100 未加载
评论 #1432288 未加载
piotrSikora将近 15 年前
Please don't use it in production, like it was already said, it's wrong on way too many levels:<p>1) This "daemon" reloads nginx (by sending "HUP" signal) every X seconds. There is nothing "dynamic" about it. Also, nginx starts new workers on each reload, but old workers are kept alive until they complete serving all requests. This means that you could end up with thousands of workers if you've got connections that take a while to complete (big files, comet servers, etc).<p>2) There is already nginx module that does exactly that (dynamically changes upstream status, starts and stops backends on demand, depending on load, etc).<p>3) nginx's cache can scale blogs much better on a single machine, there is no way to start another backend servers.