| From: | Grzegorz Jaskiewicz <gj(at)pointblue(dot)com(dot)pl> |
|---|---|
| To: | Marko Kreen <markokr(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Nikhil Sontakke <nikhil(dot)sontakke(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: gcc: why optimize for size flag is not the default |
| Date: | 2009-03-11 19:18:11 |
| Message-ID: | 3BBC3658-CCCD-4331-9CA4-06ED9C75A65B@pointblue.com.pl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11 Mar 2009, at 13:51, Marko Kreen wrote:
> Linux kernel is moving to use -Os everywhere. AFAIK their argument is
> that kernel code should not be doing anything CPU-intensive, thus
> minimal cache usage is more important than unrolled loops.
>
> This also seems to hint that -Os is not really appropriate to
> Postgres.
> Although it would be good fit for eg. PgBouncer.
while it might be right in case of linux kernel (which I won't agree
totally with personally), I don't see any reason to compare it with
postgresql.
Kernel is extensively use by everything in system, hence their
reasoning. Postgresql is an application.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | A.M. | 2009-03-11 19:31:33 | Re: gcc: why optimize for size flag is not the default |
| Previous Message | Tom Lane | 2009-03-11 17:25:20 | Re: idea, proposal: only preloadable libraries (conditional load) |