Skip site navigation (1) Skip section navigation (2)

Re: Write workload is causing severe slowdown in Production

From: "Gnanakumar" <gnanam(at)zoniac(dot)com>
To: "'Tomas Vondra'" <tv(at)fuzzy(dot)cz>
Cc: "'Merlin Moncure'" <mmoncure(at)gmail(dot)com>, "'Kevin Grittner'" <kevin(dot)grittner(at)wicourts(dot)gov>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Write workload is causing severe slowdown in Production
Date: 2012-03-23 12:25:37
Message-ID: 00a501cd08f0$11385490$33a8fdb0$@com (view raw or flat)
Thread:
Lists: pgsql-performance
> Are those wrapped in a transaction or not? Each transaction forces a fsync
> when committing, and if each of those INSERT/UPDATE statements stands on
> it's own it may cause of lot of I/O.

Yes, it's wrapped inside a transaction.  May be this could be a reason for slowdown, as you've highlighted here.  Atleast, we've got some guidance here to troubleshoot in this aspect also.

> There are tools that claim to remove the object vs. relational discrepancy
> when accessing the database. They often generate queries on the fly, and
> some of the queries are pretty awful (depends on how well the ORM model is
> defined). There are various reasons why this may suck - loading too much
> data, using lazy fetch everywhere etc.

Thanks for the clarification.

> Are you using something like Hibernate, JPA, ... to handle persistence?

No, we're not using any persistence frameworks/libraries as such.



In response to

pgsql-performance by date

Next:From: Kevin GrittnerDate: 2012-03-23 14:09:10
Subject: Re: Write workload is causing severe slowdown in Production
Previous:From: Tomas VondraDate: 2012-03-23 10:24:12
Subject: Re: Write workload is causing severe slowdown in Production

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group