Terrel Shumway wrote:
If it doesn't, a WebKit instance per-user does not sound appealing.
Instance-per-user is not a problem unless you want to host 50+ users on one box. But dedicated servers are cheap enough that you shouldn't need to put more than 10 webware users (max) on a box anyway.
I can't say this from direct experience, but I don't really see any reason 50 users would be a problem.
I can't say that from experience either -- its just a conservative estimate knowing that
1) my boxes are small, commodity servers
2) I expect my clients to be getting some decent traffic
3) I would rather underestimate and overdeliver than die when
the first publicity event hits.
4) the enlightened elite who want to run webware have enough experience
to recognize that "low-price" is not equivalent to "low-cost",
so paying $20+/mo for quality hosting is not going to throw them
for a loop.
My only concern would be memory consumption. I'd be curious what kind of memory use different people see on their sites.
Python does eat a lot of non-sharable memory. I try to reduce that by using the
shared-library build, but the compiled bytecode is still a bigger chunk.
Very quick test:
Webware python process has RSS=6168K or about 1.2% of a 512M server after responding to
ab -n 50 http://****/wk/Examples/Colors
using Python-2.3.3 w/ shared lib, Webware CVS on linux, mod_webkit2
This bears out the hypothesis that memory is the limiting resource. I would plan on 10-20
webware processes per 512MB of physical RAM, based on this not-so-real-world test.
More testing to come.
Mostly, I think Webware would scale decently alongside other products.
I don't see why it wouldn't.
I would be interested to see how PHP running as a SUEXEC CGI binary compares with Webware
(both OneShot and WebKit) on a moderately-busy site.
And separate instances give built-in clustering potential ;)
I don't see much of a win for clustering unless you are dealing with a cluster of
physical machines. In that scenario, memory and CPU resource issues take a back
seat to the complexity of managing the cluster.
Clustering is something less than 2% of web sites need to worry about anyway... By the
time *I* get there, I will have enough money to pay someone else to worry about it. 8-)
IOW, for the simple and common domain we are dealing with (i.e. "the hosting factor...")
"one instance per user per box for security and isolation purposes" does the job[1].
I guess I am becoming an "underachiever" -- Do the simplest thing that could possibly work.
-- Terrel
___________
[1] and does it *far* better than the 99% of the shared hosts out there who use mod_php with
world writable files and directories, FTP, and 1000 low-traffic sites per box. (I could do
that for $1/mo/site too if I wanted to.)
Now who wants to port Squirrelmail to Python? Anyone working on a webmail server?
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
