[Spacewalk-list] Massive problems with slow updates on rhnServerAction

Patrick Hurrelmann patrick.hurrelmann at lobster.de
Mon Oct 1 07:39:13 UTC 2012


On 20.09.2012 19:12, Paul Robert Marino wrote:
> Also did either of you tune the max open file limit
> 
> On Sep 20, 2012 1:08 PM, "Paul Robert Marino" <prmarino1 at gmail.com
> <mailto:prmarino1 at gmail.com>> wrote:
> 
>     I think I may have some idea on what may be causing this but I
>     haven't had time to look. At it yet. Did eitherof you tune the sort
>     memory or working memory in your postgres.conf
> 

Sorry for the delay, but I had to face some problems with my ovirt
test-installation. My SW 1.7 is running inside a KVM virtual machine
with 2 CPUs and 4GB RAM assigned. My PostgreSQL was tuned with pgtune
and I manually bumped the max connections to 300.

default_statistics_target = 50 # pgtune wizard 2011-12-23
maintenance_work_mem = 224MB # pgtune wizard 2011-12-23
constraint_exclusion = on # pgtune wizard 2011-12-23
checkpoint_completion_target = 0.9 # pgtune wizard 2011-12-23
effective_cache_size = 2816MB # pgtune wizard 2011-12-23
work_mem = 22MB # pgtune wizard 2011-12-23
wal_buffers = 8MB # pgtune wizard 2011-12-23
checkpoint_segments = 16 # pgtune wizard 2011-12-23
shared_buffers = 896MB # pgtune wizard 2011-12-23
max_connections = 300

Additionally I did not tune max files and there are no files pgsql_tmp.

But since I disabled all my push to clients (osad) my SW no longer
crashes that often. I still do see lots of idle transactions and hanging
update statements, but the volume is much lower now and my scheduled
nights restart of SW makes it at least survive one day.

Regards
Patrick

-- 
Lobster LOGsuite GmbH, Münchner Straße 15a, D-82319 Starnberg

HRB 178831, Amtsgericht München
Geschäftsführer: Dr. Martin Fischer, Rolf Henrich




More information about the Spacewalk-list mailing list