4 ms·
That's exactly the approach we're taking. We're not going to spend any time prematurely worrying about various scaling things until we can forecast that it's l
by ericflo 16y ago
That's exactly the approach we're taking. We're not going to spend any time prematurely worrying about various scaling things until we can forecast that it's legitimately going to be a problem.
- foobarbazetc 16y agoGreat to hear. :) While we're here, here are some PG tips: 1. Make sure your PG install is fully optimized. I've seen countless postgresql.conf's at major companies with no opts what so ever. Take a look at this book: http://www.2ndquadrant.com/books/postgresql-9-0-high-performance/ http://www.2ndquadrant.com/books/postgresql-9-0-high-perform... . 2. Make sure you're using PG 9+. 3. Use pgbouncer for connection pooling and try to write your app so you can use 'pool_mode = transaction'. 4. Please don't run PG virtualized.
- ericflo 16y agoWe're good on all fronts except 4, and the transaction pool mode :)