Thread: Testing new website code

Hi,

Those who do not believe that there is something wrong with the box
running wwwdevel, can now check for themselves.

At http://alexey.beta.postgresql.org/files/ there is the folowing:
tarball of portal directory from pgweb CVS module, some changed files
from there with profiling calls added (this needs Benchmark PEAR module,
watch the results on alexey.beta) and dump of "www" database used by
website. I am not sure whether it is a good idea to publish "gborg"
database, since it contains password hashes.

Setup instructions are in the README file available in portal tarball.

I've setup a mirror myself:
http://oc.cs.msu.su/portal/

Please note that the server running this mirror is a P2-233 with 192MB
RAM and a very slow and noisy IDE harddisk. It runs both Apache *and*
PostgreSQL and doesn't have PHP bytecode cache installed.

All this said, it generates the index page in ~0.4 second, while
alexey.beta does this in ~1 second (look at the profiling info at the
bottom of the pages).

> -----Original Message-----
> From: pgsql-www-owner@postgresql.org
> [mailto:pgsql-www-owner@postgresql.org] On Behalf Of Alexey Borzov
> Sent: 04 November 2004 10:24
> To: pgsql-www@postgresql.org
> Subject: [pgsql-www] Testing new website code
>
> Hi,
>
> Those who do not believe that there is something wrong with
> the box running wwwdevel, can now check for themselves.

You're missing the point - it's not that we don't believe something is
wrong, it's the box is not loaded enough to see the performance we've
been getting. What we're trying to do is figure what is actually wrong
whether at the OS, PHP, DB, Pear or portal code level. As you will have
seen from other posts, a couple of changes have already made significant
differences - your testing on another box indicates that there is
probably not a problem at the Pear or portal levels, thus we should
probably be looking at the OS/PHP/DB some more.

Regardsm, Dave.