On Thu, Mar 1, 2012 at 11:23 AM, Ants Aasma <ants.aa...@eesti.ee> wrote: > On Thu, Mar 1, 2012 at 4:54 PM, Robert Haas <robertmh...@gmail.com> wrote: >> ... After that I think maybe some testing of the >> remaining CommitFest patches might be in order (though personally I'd >> like to wrap this CommitFest up fairly soon) to see if any of those >> improve things. > > Besides performance testing, could you check how clocksources behave > on this kind of machine? > You can find pg_test_timing tool attached here: > http://archives.postgresql.org/pgsql-hackers/2012-01/msg00937.php > > To see which clocksources are available, you can do: > # cat /sys/devices/system/clocksource/clocksource0/available_clocksource > To switch the clocksource, just write the desired clocksource like this: > # echo hpet > /sys/devices/system/clocksource/clocksource0/current_clocksource
Sure, I'll check that as soon as it's back up. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
