On Thursday February 28, 2002 10:34 pm, Matt Feifarek wrote:
> I've got to deploy more than one webkit-app on one server.
> I know that there is webware/bin/MakeAppWorkDir.py /path/to/workdir...
> What I don't know is whether that means I have to run a completely
> different instance of the application server (on a different port, of
> course) or if it's just another place to run files from.
> The fact that it has its' own "Configs" makes me think the former.
> If so, what are the implications of this?
> Does it launch 'n' more threads of the appserver? If so, how many sets of
> 10 threads should I really run on a server?
I have a Windows 2000 test server where I'm running 13 copies of the
appserver, each in a separate working dir and each with 10 threads. No
noticeable effect on system performance. I wouldn't worry about the extra
threads -- if they aren't doing much, they will have a negligible impact on
> Do I have to install new unix-init scripts for each "workdir"?
> /etc/init.d/webkit1 and /etc/init.d/webkit2?
I assume so. On Windows I install separate "services" for each working dir,
and I assume it's analogous on Unix.
> Is there any consensus among the experts when it is time to make separate
> workdirs/appservers and when it's ok to just have contexts?
If you the apps are truly separate, there are advantages to running separate
app servers -- you can stop, update, and restart one app without affecting
the other. But it does mean one more thing to have to manage. Multiple
contexts are simpler to manage.
A question I don't know the answer to off the top of my head: do all contexts
share session storage, or are they separate session stores?