[Nottingham] Zero-PHP wiki!?

[Martin]

> ... I suspect it it just very convoluted
> database lookups from spaghetti php that is killing performance, ...

Just wondering out loud...


There's a lot of overlap in functionality between using a database and
using a plain old filesystem for the website "back end". I just wonder
what advantage having a website entirely in a database gives you other
than presumed convenience at the expense of abstraction and complexity...

Is there any significant performance difference between:

Programming to generate web pages on the fly;
Database lookup and storage of entire web pages;
Database lookup to reference web page snippets from a filesystem;
Database lookup to reference complete web pages from a filesystem;
Static website on a filesystem with database "frilly bits";
Static website.

I've listed that in the presumed performance order for first time look
up of a particular web page. I'm still thinking that the database
interaction adds a lot of overhead...

The Apache cache just looks up cache hits from a hierarchy of
directories and files in its cache. Hence, that suggests that the
filesystem wins over that of a database...


I guess I'll have to try out the http://ikiwiki.info/
 to see how well it works...


Comments welcomed,

Cheers,
Martin

-- 
----------------
Martin Lomas
martin at ml1.co.uk
----------------