Hi all. I am gifted with the quality problem of launching django site, with a forum, that will get millions of uniques per month from day one.

Will additional caching be needed to make djangobb handle the traffic? Or with the appropriate server architecture will djangobb do well right out of the box? We're going live with nginx out front(serving static media, and load balancing). Some apache servers(serving django). And a Postgres server in back.

Thanks for any input.
Cheers,
Matt

Nothing huh?

some parts is cached, sql mostly is ok, only have some troubles with search + pagination
default django cache middlewares maybe helped u

but u must tested via ab or something else with real dataset )

I mostly like nginx/cherokee + uwsgi backend (apache is old sucks ) and postgres 9+ behind pgbouncer + memcached for cache and session store (or redis)