Note that if you still have the settings you showed in your original post you're just moving the goal posts a few feet further back. Any heavy load can still trigger this kind of behaviour. On Tue, Jul 7, 2015 at 5:29 AM, eudald_v <reaven.galaeindael@xxxxxxxxx> wrote: > Hello guys! > > I finally got rid of it. > It looks that at the end it was all due to transparent_hugepages values. > > I disabled them and cpu spikes disappeared. I am sorry cause it's something > I usually disable on postgresql servers, but I forgot to do so on this one > and never thought about it. > > Thanks a lot for all your helpful messages! > > Eudald > > > > -- > View this message in context: http://postgresql.nabble.com/Sudden-connection-and-load-average-spikes-with-postgresql-9-3-tp5855895p5856914.html > Sent from the PostgreSQL - performance mailing list archive at Nabble.com. > > > -- > Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance -- To understand recursion, one must first understand recursion. -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
