From: | tv(at)fuzzy(dot)cz |
---|---|
To: | "Corin" <wakathane(at)gmail(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: mysql to postgresql, performance questions |
Date: | 2010-03-18 14:50:53 |
Message-ID: | 57784.193.179.187.70.1268923853.squirrel@sq.gransy.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
I guess we need some more details about the test. Is the
connection/disconnection part of each test iteration? And how are the
databases connected (using a socked / localhost / different host)?
Anyway measuring such simple queries will tell you almost nothing about
the general app performance - use the queries that are used in the
application.
> I also wonder why the reported runtime of 5.847 ms is so much different
> to the runtime reported of my scripts (both php and ruby are almost the
> same). What's the best tool to time queries in postgresql? Can this be
> done from pgadmin?
I doubt there's a 'best tool' to time queries, but I'd vote for logging
from the application itself, as it measures the performance from the end
user view-point (and that's what you're interested in). Just put some
simple logging into the database access layer.
regards
Tomas
From | Date | Subject | |
---|---|---|---|
Next Message | Kenneth Marshall | 2010-03-18 15:00:17 | Re: mysql to postgresql, performance questions |
Previous Message | Corin | 2010-03-18 14:31:18 | mysql to postgresql, performance questions |