On Thu, Mar 29, 2012 at 12:02 PM, Campbell, Lance wrote:
> I forgot to mention that the slowdown in particular for other applications
> is when they are trying to insert or update tables unrelated to the
> application mentioned in my prior application that does the massive small
> inserts.
It sou
Lance,
Have faced the same issue with thousands of small inserts (actually they were
inserts/updates) causing the database to slowdown. You have received good
suggestions from the list, but listing them as points will make the issue
clearer:
1) Disk configuration: RAID 5 was killing the perfor
On 03/29/2012 03:27 PM, Bob Lunney wrote:
Lance,
May small inserts cause frequent fsyncs. Is there any way those small
inserts can be batched into some larger sets of inserts that use copy
to perform the load?
Or possibly a prepared statement called many times in a single
transaction,
Lance,
May small inserts cause frequent fsyncs. Is there any way those small inserts
can be batched into some larger sets of inserts that use copy to perform the
load?
Bob Lunney
From: "Campbell, Lance"
To: "Campbell, Lance" ; "pgsql-performance@postgresql.
On a Linux system you can use tools like "sar" and "iostat" to watch
disk activity and view the writes/second or I am sure there are other
tools you can use. Watch CPU and memory with "top" If it does appear
to be an I/O issue there are
some things you can do in either hardware or software, or if
can you post all the configuration parameters related to the I/O activity?
plus, could you post some stats from 'iostat' when this is happening?
thx
On Thu, Mar 29, 2012 at 9:02 PM, Campbell, Lance wrote:
> I forgot to mention that the slowdown in particular for other
> applications is when the
I forgot to mention that the slowdown in particular for other applications is
when they are trying to insert or update tables unrelated to the application
mentioned in my prior application that does the massive small inserts.
Thanks,
Lance Campbell
Software Architect
Web Services at Public Aff
PostgreSQL 9.0.x
We have around ten different applications that use the same database. When one
particular application is active it does an enormous number of inserts. Each
insert is very small. During this time the database seems to slow down in
general. The application in question is inser
