Andrew Piskorski said:
more complicatd of course, but if you were going to end up using, say 3
* 2 cpu FreeBSD front-end web server boxes, that's no different than how
you'd run 6 * 1 cpu Linux boxes.
There likely will be a big difference, the 6*1 CPU solution is likely
cheaper and delivers
394 nsconf.nsd = (char *) Tcl_GetNameOfExecutable();
(dbx) next
trace in nsmain.c: 395 NsConfigEval(config, argc, argv, optind);
stopped in Ns_Main at line 395 in file
/aolserver_devel/aolserver-4.0-beta10-src/nsd/nsmain.c ($t1)
395 NsConfigEval(config, argc, argv,
And when the proxy daemon driver was first introduced that additional
communication overhead mentioned above turned out to be horrendous, though
it
got greatly speeded up soon after that discovery. I remember because I'm
the
one who flagged that fact when comparing throughput of that driver
On 2003.11.10, Kenneth Snyder [EMAIL PROTECTED] wrote:
Ok, that made complete sense, Figured that out (dbx:multproc on)
Cool. Yeah, that's it ...
It passes to the child and moves along a little, then
Here's what happens:(dbx) next
trace in nsmain.c: 394 nsconf.nsd = (char *)
I built the tcl. . threads were enabled. TCL8.4.4.
I tried the 20mB stack, same results...
What's the default stacksize, as on my AOLserver 3.5.5 installation on
my AIX4.3.3 machine, that stacksize line is commented out. I tried that
here too, same results.
Now that you mention it, I think I had
--- Andrew Piskorski [EMAIL PROTECTED] wrote:
Um, so you're saying the advantage to an external db
driver here is
that AOLserver + db driver now consists of two
processes rather than
one, so they will make more efficient use of
FreeBSD's inferior
threading model on a dual cpu machine?
On Tue, Nov 11, 2003 at 09:20:39AM -, Bas Scheffers wrote:
Andrew Piskorski said:
more complicatd of course, but if you were going to end up using, say 3
* 2 cpu FreeBSD front-end web server boxes, that's no different than how
you'd run 6 * 1 cpu Linux boxes.
There likely will be a
On Tue, Nov 11, 2003 at 10:00:12AM -0800, Nathan Seven wrote:
Um, so you're saying the advantage to an external db driver here
is that AOLserver + db driver now consists of two processes rather
than one, so they will make more efficient use of FreeBSD's
inferior threading model on a dual
that clear. I wasn't aware of that, I'd incorrectly assumed that the
proxy daemon was a single multi-threaded process.
The external proxy scheme was invented to be able to use databases which
were hostile to in-process use, either because they were not thread-safe,
or because they are
Greetings,
We've been using AOLserver with Oracle in Unix/Sun platform; recently we've
attempted to expand our servers with running AOLserver (3.4.2) on
Intel/Linux (RH 6.2 7.1), while the performance is good and all of our
application seem to work on this stack, the major issue has been
On Tue, Nov 11, 2003 at 11:24:47PM -0500, Seena Kasmai wrote:
process, we found the cause of these crashes, and that is: selecting an
empty clob using ACS API (or ns_db process). Running the same query via
SQL/Plus from this Linux box, works fine.
Don Baccus exaplained here that the
11 matches
Mail list logo
