Re: Reasons to choose CLISP over other free implementations

On Wed, 28 Nov 2007 12:16:36 -0800, Slobodan Blazeski wrote:
- No threads so forget about web development.

It really depends on the architecture. You can build pretty large and
fast web apps using just "old school" multi-process systems. The real
advantage of threads is the fast sharing of large sets of peristent data,
which you may not do all that much. For many tasks, using a single SQL
database backend (with something like memcached thrown in when you need
it) is enough. Plus, it's usually trivial to spread those systems across
multiple servers.

The only time I've really needed to use threads for a web app was when
the amount of shared data was large and specialized enough that querying
it via the database was getting too slow and could obviously be improved
by using better suited algorithms, small enough to fit into memory (about
5 .. 10 Gb) and too large to be copied across multiple processes on an 8-
core 16Gb machine. And even then the whole multi-thread system was
separated out so we could move and duplicate it to multiple machines.

* disclaimer: this was a mostly perl/C++ system, but I think the
principle is more or less the same.

Joost.

.

Relevant Pages