| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "Oleg Bartunov" <oleg(at)sai(dot)msu(dot)su> |
| Cc: | "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>, "Gavin M(dot) Roy" <gmr(at)ehpg(dot)net>, "Magnus Hagander" <mha(at)sollentuna(dot)net>, "Josh Berkus" <josh(at)agliodbs(dot)com>, <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: pgfoundry moved ... |
| Date: | 2005-04-29 08:12:26 |
| Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E490DA0D@ratbert.vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
> -----Original Message-----
> From: Oleg Bartunov [mailto:oleg(at)sai(dot)msu(dot)su]
> Sent: 29 April 2005 05:42
> To: Dave Page
> Cc: Marc G. Fournier; Gavin M. Roy; Magnus Hagander; Josh
> Berkus; pgsql-www(at)postgresql(dot)org
> Subject: Re: [pgsql-www] pgfoundry moved ...
>
> Is't possible to understand what's an actual problem, database or
> web part ? Is't possible to see timings for typical longest queries ?
> Probably there is some profiling support which show timings for
> each component used. If gbord would be Mason based
> applications it could be
> done very easy.
We've spent time on that in the past, and nothing obvious is apparent,
other than disk IO being slow in general. The same problem was seen when
svr2 was on one of Marc's boxes. I'm fairly convinced it's a unionfs
issue.
Regards, Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2005-04-29 14:35:18 | Re: pgfoundry moved ... |
| Previous Message | Oleg Bartunov | 2005-04-29 04:41:55 | Re: pgfoundry moved ... |