On 23 Březen 2012, 11:10, Gnanakumar wrote: > First off, thank you *so much* for that detailed explanation comparing > with > a real-time application performance benchmark, which was really > enlightening > for me. > >> How are you handling concurrency? (Are you using FOR SHARE on your >> SELECT statements? Are you explicitly acquiring table locks before >> modifying data? Etc.) You might be introducing blocking somehow. > > No, actually am not explicitly locking any tables -- all are *simple* > select, update, insert statements only. 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. >> Besides the outdated PostgreSQL release and possible blocking, I >> would be concerned if you are using any sort of ORM for the update >> application. You want to watch that very closely because the >> default behavior of many of them does not scale well. There's >> usually a way to get better performance through configuration and/or >> bypassing automatic query generation for complex data requests. > > Am not able to understand above statements (...any sort of ORM for the > update application ...) clearly. Can you help me in understanding this? 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. Are you using something like Hibernate, JPA, ... to handle persistence? Tomas -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
