JP <[EMAIL PROTECTED]> wrote: > Sounds like an interesting setup! Maybe off topic, but, would you care > to elaborate on that topic? Server configuration, virtualization > software running, etc.? >
The http://www.sqlite.org/ website runs on a leased virtual server. The virtual server is leased from http://www.linode.com/ and is a Linode 160. This is roughly a 200MHz machine with exactly 160MiB of RAM and about 8GiB of disk space. There are around 19 or so equivalent virtual machines running on the same physical box. The same virtual server hosts multiple websites. Besides SQLite it hosts: http://www.cvstrac.org/ http://canvas3d.tcl.tk/ http://tkhtml.tcl.tk/ And there are other proprietary sites on the same VM. But most of the load comes from SQLite. On a typical weekday, the SQLite website is visited by around 6000 distinct IP addresses and takes 70000 or so hits. Total traffic is around 1.7GiB per day. The webserver is a custom one-file server, the source for which can be found at: http://www.sqlite.org/althttpd.c The webserver is launched from inetd. Thus, a new process is forked for each incoming connection. This is not the most efficient way to handle http requests, but it is perfectly adequate for the kind of traffic that www.sqlite.org sees - only one request per second. The althttpd webserver handles direct files delivery or CGI. Nothing fancy. There is a single unified log file. Althttpd runs each request in a chroot jail for security. CVSTrac (http://www.cvstrac.org/) is used for version tracking, tickets, and wiki. An older version of CVSTrac is currently used - one that uses SQLite version 2. The SQLite database file that backs up this CVSTrac instance is about 30MiB in size. -- D. Richard Hipp <[EMAIL PROTECTED]>
