From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | Jayashankar K B <Jayashankar(dot)KB(at)lnties(dot)com>, Andy Colson <andy(at)squeakycode(dot)net>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Postgress is taking lot of CPU on our embedded hardware. |
Date: | 2012-01-28 02:23:45 |
Message-ID: | CAGTBQpYe6yLY2xGx6ZthnuLR-YkXXospveqb897H+UMEdjfYNw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Fri, Jan 27, 2012 at 4:56 PM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> I don't think there's anything particular in postgres that would make it a
> poor choice on a small system, as far as CPU usage is concerned anyway. But
> inserting rows in a database is certainly slower than, say, writing them
> into a flat file.
How did you install postgres?
Did you build it?
Which configure flags did you use?
Exactly which m68k cpu is it? (it does matter)
For instance...
wiki: "However, a significant difference is that the 68060 FPU is not
pipelined and is therefore up to three times slower than the Pentium
in floating point applications"
This means, if you don't configure the build correctly, you will get
really sub-optimal code. Modern versions are optimized for modern
cpus.
Of utmost importance, I would imagine, is the binary format chosen for
pg data types (floating types especially, if you use them).
From | Date | Subject | |
---|---|---|---|
Next Message | Jon Nelson | 2012-01-28 02:34:16 | Re: regarding CLUSTER and HUGE work_mem / maintenance_work_mem |
Previous Message | A.M. | 2012-01-27 20:09:26 | Re: pl/pgsql functions outperforming sql ones? |