In case anyone is still interested, I was able to improve the load considerably by wrapping a group of 10-15 INSERTS into a single transaction. I didn't know that each insert/query not explicitly wrapped in a transaction got it's own transaction (and the associated overhead) by default. Load is now back to around 0.25 or thereabouts. Traffic is growing very rapidly, so I don't know how long it will stay at 0.25. FYI, Brian -- [EMAIL PROTECTED] http://www.baquiran.com US Fax: (603) 908-0727 AIM: bbaquiran
- [ADMIN] Tuning postgres for high volume applications Brian Baquiran
- Re: [ADMIN] Tuning postgres for high volume applic... Brian Baquiran
- Re: [ADMIN] Tuning postgres for high volume applic... Guido Goldstein
- Re: [ADMIN] Tuning postgres for high volume applic... Chris Albertson
- Re: [ADMIN] Tuning postgres for high volume applic... Hernan J. Gonzalez
- Re: [ADMIN] Tuning postgres for high volume ap... Brian Baquiran
- [ADMIN] Reducing the search results to a c... Ruben Fagundo
- Re: [ADMIN] Reducing the search result... Chris Albertson
- Re: [ADMIN] Reducing the search result... Evilio del Rio
- Re: [ADMIN] Tuning postgres for high volum... Peter Vazsonyi
- Re: [ADMIN] Tuning postgres for high volume ap... Garry Dolley
