256 megs should be more then enough for a low-traffic site like that on
OpenBD. A default install of OpenBD (without additional sites added to
it) is just about 50 megs of RAM. That's Tomcat and OpenBD together,
which is an extremely small amount of overhead.
What I've seen over time is that some sites take quite a bit of memory
to load initially (like loading up a framework or something), but after
that initial load, things run just fine on even a very small amount of
RAM, you just need that big memory hit at the beginning - which is fine
as long as you have some swap to go into.
>> [1] Our host is all SAN-based, so no swapping allowed. (!)
This confuses me. Why would you not be allowed to have swap on a SAN?
There is no technical reason that I'm aware of to not have swap on a
SAN. It would most likely be because the sysadmin doesn't want to give
out SAN space as swap, or because the virtualization software you're
using is the kind that plays tricks with your memory instead of
allocating a true swap partition. If your host has a technical
explaination for this, I'd love to hear it.
Bottom line, not having true memory and swap is hurting you. It would be
better to have a lower amount of memory that you could actually use then
this fake sort of memory that you have now.
Warm regards,
Jordan Michaels
Vivio Technologies
http://www.viviotech.net/
Open BlueDragon Steering Committee
Railo Community Distributions
Göran wrote:
Im no Tomcat guru, but I have read the documentation and have
experimented and tweaked the Java setings on some Linux servers
(Ubuntu/Tomcat 6/openBD 1.2).
If you have a tomcat start script, preferebly a start/stop script in /
etc/init.d/tomcat. Then you should have a CATALINA_OPTS setting there
as well as a JAVA_HOME like this:
export JAVA_HOME=/usr/lib/jvm/java-6-sun
export CATALINA_OPTS="-Xms512m -Xmx512m"
I don´t think Tomcat use the settings in setenv.sh or you have to add
a CATALINA_OPT.
I am also running a small VPS with 256 RAM, and have a similar memory
alocation that you have. But I only have a old BD 7 there.
My advice is that you first verify that your settings is picked up by
Tomcat.
On 17 Jan, 02:03, Derek Warren <[email protected]> wrote:
Hello OpenBDers,
I'm a stranger in a strange land when it comes to OpenBD and Apache
Tomcat, so I'm looking for some advice regarding minimum memory
requirements.
I lend a hand with a non-profit group that runs a small site with
OpenBD, where "small" means less than ~400 unique visitors/day or
about 1,000 page views daily. We have a CentOS 4.x virtual private
server with 768MB of RAM allotted, leaving 400MB for OpenBD 1.2 and
Tomcat 6.0.20.
setenv.sh is set to the defaults provided by the Viviotech OpenBD
installer:
JAVA_OPTS="-Xms128m -Xmx256m"
According to `top`, Tomcat's resident memory size hits about 110MB
before it goes into 'perpetual garbage collection mode', eating 100%
CPU time on 2 cores. D'oh! I can't blame it--as soon as the startup
script executes, we're down to 0KB of free RAM without having served a
single page!
My question: Given that money may not be abundant, what would your
recommendation be for a minimum amount of free RAM for OpenBD to play
with? "As much as possible", of course, but we may have to cut or or
farm out some services instead.
If there are any other relevant details that would help, please let me
know.
Many thanks for your input,
--Derek
[1] Our host is all SAN-based, so no swapping allowed. (!)
[2] Our host allows us to go beyond our allotted 768MB of RAM if the
hypervisor sees that other VPS instances are not using all their
allotted RAM. I'm guessing we're in this situation because the box is
more crowded these days, and also because our control panel software
has continually upgraded mail and anti-spam services, etc., to newer
versions, all of which consume a little more memory than their older
counterparts.
--
[http://derek.trideja.com/buxton-sig.mov]
--
Open BlueDragon Public Mailing List
http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon
mailing list - http://groups.google.com/group/openbd?hl=en
!! save a network - please trim replies before posting !!