>fact that the number of fields stays constant?
That is part of it. The other part is given the structure of a bbs system, we know what data we need based on the url. Using that, we allow the highly optimized file system to do the work of locating the data (the file). With a db, it has to find the data, then work the file system to retreive the data, and possibly decompress it. By using the file system to go straight to the data, we eliminate one or two steps and take advantage of builtin perks like disk caching.
Comparatively, I would suggest that this software could handle 5 to 10 times the load that a leading MySql based bbs can. The MySql/DBI based prototype I have built of this software is far slower. I would never put a SQL based BBS online without twice the box and the ability to cache the entire db in ram.
Unknown. Let me finish the thing first and see what we have.
No, it's a fully managed server.
runs about 300 meg in "slim" mode (logs and extraneous foo files cleaned), and could pop well above 500 if I don't keep things tidy. Bandwidth, around 2+ gig a day + another 200meg in graphics that are on another server.
[edited by: Brett_Tabke at 3:42 am (utc) on Aug. 7, 2002]