Re: Late night problems

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>, <pgsql-www(at)postgresql(dot)org>
Subject: Re: Late night problems
Date: 2004-06-28 11:07:45
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E40C376C@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

> -----Original Message-----
> From: pgsql-www-owner(at)postgresql(dot)org
> [mailto:pgsql-www-owner(at)postgresql(dot)org] On Behalf Of Greg
> Sabino Mullane
> Sent: 28 June 2004 11:49
> To: pgsql-www(at)postgresql(dot)org
> Subject: Re: [pgsql-www] Late night problems
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> > I don't see this from .uk. In fact, search.postgresql.org has just
> > recently been moved to new hardware in .au which offers far greater
> > performance - for example, I just searched then entire database for
> > 'referential integrity' and saw the results page, including
> all images
> > and ads in about 3 seconds.
>
> Seems to be better now. Just now, searching for "speed" in
> the archives took "0.060" seconds according to the results
> pae. Last night, it took 108 seconds. Even navigating from
> one message to the next in a thread took about 20 seconds for
> each page to load. This has happened
> before: I'll whip up a cron script to track basic
> responsiveness over time.

OK, that sounds like it'll be useful. Might be worth talking to John
Hansen (who's on this list now) about it seeing as he's donating all the
CPU/disk/connectivity...

Regards, Dave.

Browse pgsql-www by date

  From Date Subject
Next Message John Hansen 2004-06-28 11:46:07 Re: Late night problems
Previous Message Greg Sabino Mullane 2004-06-28 10:49:26 Re: Late night problems