| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Yang Zhang <yanghatespam(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Sorting performance vs. MySQL |
| Date: | 2010-02-22 20:45:13 |
| Message-ID: | dcc563d11002221245u36db3560t7886f3f8b0ed9735@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Feb 22, 2010 at 12:53 PM, Yang Zhang <yanghatespam(at)gmail(dot)com> wrote:
> On Mon, Feb 22, 2010 at 2:52 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
>> On Mon, Feb 22, 2010 at 11:10 AM, Yang Zhang <yanghatespam(at)gmail(dot)com> wrote:
>>> I have the exact same table of data in both MySQL and Postgresql. In Postgresql:
>>
>> Just wondering, are these on the same exact machine?
>>
>
> Yes, on the same disk.
I'm wondering how much of this could be caching effects. Is the MySQL
database "warmed up" before you started, and the pgsql database is
"cold" and no caching has taken place?
What do things like vmstat 10 say while the query is running on each
db? First time, second time, things like that.
Also, just curios, what's shared_buffers set to on the pgsql instance?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yang Zhang | 2010-02-22 20:55:54 | Re: Sorting performance vs. MySQL |
| Previous Message | Tom Lane | 2010-02-22 20:44:23 | Re: Sorting performance vs. MySQL |