Jeffrey,

> I agree that some instrumentation of the backend might be needed.  But
> several of the performance-critical parameters seem tractable:
>
> Effective cache size - should be easy to monitor the system for this
> Shared buffers - easy to start from a rule-of-thumb and monitor usage
> Work mem - trace the size and frequency of temp files
> Wal buffers - trace the average or 80th percentile number of pages
> generated by transactions
> Commit delay - track the concurrency level and avg distance btw commits
> Checkpoint segments - should be very easy to auto-adjust
> Random page cost - should possible to determine this at runtime
> Vacuum* - may be possible to determine vacuum impact on concurrent
> queries

Great.  Wanna join the configurator project?  I won't have much time to 
work on it before March, but anyone with ideas is welcome.

-- 
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faq

Reply via email to