Stefan de Konink wrote, On 10/16/2012 06:49 PM:
On Tue, 16 Oct 2012, Assaf Gordon wrote:
Assuming the "user" time is the time "wasted" by the client program (psql/mclient), and assuming "sys" time is negligible, then subtracting the "user" time from the "real" time gives an indication of how much time the server took to complete the query and transfer the results.
What about: the time taken to serialise the results? For MonetDB this is done in a very 'plain text' wire-format.
Indeed, that could explain some of the differences, but: 1. I need to take the entire process into account, because whether I use "mclient" or Perl (for my website), the results will have to be transferred somehow. If the serialization is the bottle-neck, perhaps there are other ways to work around it? 2. Serialization alone doesn't explain test #6, where a query for a single row with 138 columns takes 9 seconds to complete.
Are you aware of the PostgreSQL \timing command? In that way you can see outputs similar to that of MonetDB with respect of time taken for a query.
Thanks for the tip, I'll try to rerun the tests with that. -gordon _______________________________________________ users-list mailing list users-list@monetdb.org http://mail.monetdb.org/mailman/listinfo/users-list