Matthew wrote:
> Confluence and JIRA both need a decent sized heap.
Amen to that, brother. ;-)
> One possibility
> would be to use a beefy server with a shared JVM for 5-10 instances.
CPU hasn't been a big problem... but RAM seems to go like hotcakes at a
lumberjack convention.
> My concern is that application server problems, maintenance, and
> stability now impact multiple customers. Also, it bothers me
> that one
> user could hog a majority of the application memory space.
Yeah... I almost suggested that if folks wanted to share a server, we
might chip in and buy one to share, but after some quick calculations --
it's going to be a tough thing to do and keep folks happy.
> Any ideas and/or suggestions? If we start putting something
> together, perhaps we will give away a few accounts for testing!
Somebody suggested virtual hosting like Xen or VMWARE... and that might
be a good way to go, but also seems like a fair bit of overhead. Plus, I
wonder if Atlassian's license is flexible to accomodate multiple
"virtual" servers.
Since as I said, CPU doesn't seem to be a limiting factor -- perhaps a
modest box loaded with RAM to the gills could support 20-30 JVM's? Split
the customers into separate JVM's ...at least that eliminates the
problem of one customer problem or RAM usage affecting another customer.
Also -- perhaps Jetty or Resin would help on the RAM issue -- just
guessing here - I only have Tomcat experience, but folks who use those
other two generally are cult-like in their love for them. (kinda like
Volvo-owners)
Lastly...getting back down in scale to little guys like me... I just
want "one or two spaces". So as long as the machine is moderately
responsive, I'd be happy.
So maybe one big honkin' box with one unlimited license install,
security groups setup so that only *I* can edit and admin my spaces.
There are some admin tasks that I'd want to have access to that "Space
Admins" can't do yet (ex. add plugins and macros)... so there would be
limitations/pains while the Atlassian boys caught up on this new
"service provider" model.
And there would obviously be chances for pain when one user brought down
the entire user-server.... but maybe you could get a bit of legalese
that folks need to sign which gives you guys some room to slide.
Since nobody else is doing shared hosting ... I'd personally agree to
some 'bumps' along the way. Maybe others would too...hard to say.
At any rate, good luck with the hosting! :-)
Cheers,
Timo
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
confluence-user details available at:
http://www.atlassian.com/software/confluence/mailinglist.jsp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~