On Apr 17, 2006, at 6:37 PM, Andrew Piskorski wrote:
On Mon, Apr 17, 2006 at 10:47:45AM +0100, John Buckman wrote:
ns_cache creates a per-thread global, which is not quite the same
thing, as sometimes the same thread will use a different interpreter.
Hm, under what circumstances have you
On Apr 17, 2006, at 3:43 PM, carl garland wrote:
Why can't you just do this in your config file:
ns_section ns/server/${servername}/adp
ns_param map * ;# Any extension can be mapped.
This should not interfere with deliverty of any registered mime types
and should be as fast if
On Apr 17, 2006, at 2:46 PM, Andrew Piskorski wrote:
On Mon, Apr 17, 2006 at 10:47:45AM +0100, John Buckman wrote:
Is there any way in AOLSserver 4 to have per-tcl-interpreter global
variables?
You already do. Tcl global variables are per-thread, which is also
per-interpreter.
I don't
Is it possible to build AOLServer in a single-threaded, lock-free
manner?
Because BerkeleyDB's tcl interface isn't thread safe, I'm running
aolserver in single-thread mode, with
ns_param maxthreads 1
ApacheBench shows me getting 440 page requests per second, on an ADP
page that does a
John Buckman said:
Because BerkeleyDB's tcl interface isn't thread safe, I'm running
aolserver in single-thread mode, with
You need to look into environments in the Berkely DB system. The way I
see it, you should be able to have concurrent access to one database from
many threads in AOLserver.
On Tue, Apr 18, 2006 at 08:46:39AM +0100, John Buckman wrote:
Is it possible to build AOLServer in a single-threaded, lock-free
manner?
I would be really, truly astonished if any such change was even
vaguely possible without lots of very serious, hard-core hacking.
My guess is the only
On Apr 18, 2006, at 10:32 am, Andrew Piskorski wrote:
On Tue, Apr 18, 2006 at 08:46:39AM +0100, John Buckman wrote:
Is it possible to build AOLServer in a single-threaded, lock-free
manner?
My guess is the only remotely plausible way, short of redesigning and
reimplementing everything from
On Apr 18, 2006, at 9:55 am, Bas Scheffers wrote:
You need to look into environments in the Berkely DB system. The
way I
see it, you should be able to have concurrent access to one
database from
many threads in AOLserver.
The -threads command, which enables thread safety in Berkeley DB
John Buckman said:
440 hits/s second is plenty fast, amazing even (fyi, compared to
about 12 hits/s I get if I code the same page in MySQL), I was just
What kind of SQL/code is that? And what kind of server? I get 100+
pages/sec using AOLserver and Postgres for a message board system; two
Wow, what a subject line that is!
This might help shed some light on the problem:
http://philip.greenspun.com/wtr/aolserver/introduction-1.html
tom jackson
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to [EMAIL PROTECTED]
with the
body of
10 matches
Mail list logo
