Re: Archives too slow

I can confirm the performance currently is terrible.

---------------------------------------------------------------------------

Greg Sabino Mullane wrote:
[ There is text before PGP section. ]
>
[ PGP not available, raw data follows ]
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> I am not happy with how slow the archives site is. It reflects
> bad on PostgreSQL and supports the stereotype of PG being "slow".
> For example, this page:
>
> http://archives.postgresql.org/pgsql-hackers-win32/2004-07/msg00003.php
>
> took 27 seconds to load completely. Some days, the times are better, but
> it always takes a notieeable delay for the page to load. It also seems
> to load in three sections: the top banner ad / search box, the title
> and header section, and then the rest of the page. The first two load
> today in about 10 seconds, the third about 16 seconds after that.
> Subsequent hits tend to be much faster (disk caching one presumes), so
> if you test, change the above URL to a random month, day, and message.
> I don;t think it is on my end: I'm on a very fast connection, and (for
> comparison) pgsql.ru loads very, very fast, and runs it searches of
> the entire archives faster than arhives.postgresql.org can display
> a single message.
>
> - --
> Greg Sabino Mullane greg(at)turnstep(dot)com
> PGP Key: 0x14964AC8 200408281951
> -----BEGIN PGP SIGNATURE-----
>
> iD8DBQFBMRs3vJuQZxSWSsgRAgTqAJ4rjb9HpR+glJS4y4fGYrTLnahIxwCgjrUv
> WteQbp0fd3QaZPbVb5wZM+4=
> =puf4
> -----END PGP SIGNATURE-----
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
[ Decrypting message... End of raw data. ]

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073