Hacker News Reader

The funny part is trac isn't that fast either. It's overall a superior tool for the job, and loads simpler in every respect, but I get a healthy amount of delay on each and every action I perform in most trac deployments.

I keep meaning to take time out one of these weekends to profile and determine how to mitigate this, but it's just not a priority.

View on HN

Switch to the postgres backend. The default sqlite one can get quite slow in high concurrency situations, although I've actually had 50 peple running quite happily off the sqlite backend.

Present concurrency is 0, it's just slow. It's not SQLite unless there is pathological behavior because I've demoed ideas to HN traffic with SQLite before and it performed better than a vanilla MySQL deployment. (Not saying this is advisable, just that SQLite isn't at fault unless Trac is doing something stupid.)

Are you positive switching to the postgres backend will help when there's almost no concurrency and the slowness is persistent and deterministic?

All I'm saying is that it worked for me.

How are you hosting it? I'm using Apache 2.2 with mod_wsgi on Ubuntu 10.04LTS. Don't use mod_python - it's terrible.

Reply on news.ycombinator.com