Comments on: Rapid development serving 500,000 pages/hour

By: Robin Jakobsson

Robin Jakobsson — Tue, 03 Mar 2009 11:00:13 +0000

Nice post!
Have you been thinking of optimizing the front end at Curse.com? CSS sprites and the likes?

Cheers

By: lucasjosh.com » Blog Archive » Links for 1/30/08 [my NetNewsWire tabs]

lucasjosh.com » Blog Archive » Links for 1/30/08 [my NetNewsWire tabs] — Thu, 31 Jan 2008 05:14:01 +0000

[...] Rapid development serving 500,000 pages/hour | David Cramer.net [...]

By: Valentino

Valentino — Wed, 23 Jan 2008 22:59:10 +0000

And for alternative solutions to clustering and replication have a look at this page, it may help, otherwise… I just tried

http://developer.postgresql.org/index.php/Replication,_Clustering,_and_Connection_Pooling

By: Valentino

Valentino — Wed, 23 Jan 2008 22:38:51 +0000

About PostgreSQL scaling better than Mysql:
http://tweakers.net/reviews/657/1/database-test-dual-intel-xeon-5160-pagina-1.html
Here it’s pretty clear what scales better and postgresql 8.3 is even faster (a lot) than the one used in the test.

By: tijs.org » Blog Archive » links for 2007-05-25

tijs.org » Blog Archive » links for 2007-05-25 — Wed, 30 May 2007 04:42:07 +0000

[...] Rapid development serving 500,000 pages/hour at DavidCramer.net (tags: toread django performance scaling python) [...]

By: SuperJared

SuperJared — Mon, 28 May 2007 19:10:14 +0000

Let me first say that I use Django for every thing that I can. However, I’d like to mention that Smarty works quite well if used properly, allowing templates to be cached. I remember back in 2004 I had a site that was getting nearly 300 req/s using a Smarty-templated site.

Now, given the choice I would NEVER use Smarty again simply because I would hope to never use PHP again. Python/Django is just too… amazing… Words.. can’t describe. Should have sent… a poet.

By: Django Utilidades

Django Utilidades — Sat, 26 May 2007 20:55:34 +0000

500.000 page views por hora…

Ã“timo case em Django.
Em dezembro Ãºltimo, este site: [1]Â teve vÃ¡rias quedas por ter requisiÃ§Ãµes demais. Tomaram a decisÃ£o de mudar de ferramenta, e escolheram o Django.
A decisÃ£o foi acertada e pode ser verificada aqui: [2] [3]
Links relaciona…

By: David

David — Fri, 25 May 2007 23:26:52 +0000

Smarty is the paint on a car, where as Django is the tight suspension, quick accelerating roadster

By: Soltys

Soltys — Fri, 25 May 2007 21:11:25 +0000

Nice score…
Probably if you choice Smarty not Django, server could not hang too much visits/hits.

By: Extenuating Circumstances » Blog Archive » links for 2007-05-25

Extenuating Circumstances » Blog Archive » links for 2007-05-25 — Fri, 25 May 2007 10:25:49 +0000

[...] Rapid development serving 500,000 pages/hour at DavidCramer.net (tags: performance development python scaling django availability lamp) [...]