-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 And if you have sites frequently under heavy load then chances are a shared server isn't a good idea anyway.
exactly. David E Jones sent the following on 3/31/2009 3:16 PM: > > What does peak CPU have to do with it? All programs use significant CPU > time every now and then... but usually not for long periods of time. App > servers typically don't use much CPU time unless they are under heavy > load... and if you have sites frequently under heavy load then chances > are a shared server isn't a good idea anyway. So, what's the point? > > -David > > > On Mar 31, 2009, at 4:13 PM, BJ Freeman wrote: > > sounds like you got it working on shared server, based on my experience > when seems lot less than yours, I don't see how more than one instance > can share when another instance is running 70-90% cpu, at peak times. > > I would guess it is like a bare-bones system with out many threads, or > activity. > > > David E Jones sent the following on 3/31/2009 1:34 PM: >>>> >>>> OFBiz will definitely work on a shared server, I've worked with dozens >>>> of clients who have done that. It isn't too hard to fit half a dozen >>>> instances on a single low-end (but modern) server, with databases for >>>> each too. Of course, shared server approaches are as varied as holidays >>>> around the world and there are many variations where OFBiz would not >>>> run. >>>> >>>> Running in 256M would be pretty tight, even for a low-traffic site. Is >>>> that the amount of memory available to the OS, or to the JVM? If it is >>>> the memory available to the OS, and if there is no database also running >>>> on the box (which would definitely make 256M too little), then the -Xmx >>>> parameter should be about 2/3 of your memory (the 256M). If that is the >>>> amount available to the JVM, then set -Xmx to 256M, and -Xms to the same >>>> thing (on a dedicated server no use having Java play with expanding and >>>> contracting the memory it uses). >>>> >>>> -David >>>> >>>> >>>> On Mar 31, 2009, at 1:44 PM, BJ Freeman wrote: >>>> >>>> as the startofbiz.sh says. 128megs minimum. >>>> Xms128M -Xmx512M >>>> Ofbiz will not work on a shared server. >>>> there are times it will use 70-90% of the CPU time. >>>> >>>> Branden Strickland sent the following on 3/31/2009 9:10 AM: >>>>>>> All, >>>>>>> >>>>>>> It's been a while since I've worked with OFBIZ but the time has >>>>>>> come to >>>>>>> resume working with it. >>>>>>> >>>>>>> I know the answer to my question (sort of) but need some guidance >>>>>>> from some >>>>>>> good JAVA guys... (YOU!) >>>>>>> >>>>>>> Overview: >>>>>>> Godaddy's virtual dedicated servers are setup with virtuoso, they >>>>>>> alocate >>>>>>> only the needed memory up to what you have for max (me = 256mb) This >>>>>>> should >>>>>>> be fine as I've gotten a test box with that to run OFBIZ. >>>>>>> >>>>>>> I have everything setup; Ant, JDK1.6,ofbiz svn exported. >>>>>>> Centos 5 >>>>>>> >>>>>>> When I go to do an ant run-install-seed I get: >>>>>>> >>>>>>> Error occurred during initialization of VM >>>>>>> Could not reserve enough space for object heap >>>>>>> Could not create the Java virtual machine. >>>>>>> >>>>>>> I've inserted an alias into my /etc/profile.d/java.sh (same as bashrc >>>>>>> but >>>>>>> cleaner for CENT/RHEL products) so that I have: >>>>>>> export JAVA_HOME=/opt/jdk1.6.0_13/jre >>>>>>> PATH=$PATH:$JAVA_HOME/bin >>>>>>> alias java='java -Xms2m -Xmx16m' >>>>>>> >>>>>>> I'm told the Xms and Xmx will help lower the memory hogging that java >>>>>>> wants >>>>>>> to do, but I'm having little success. I'm fine with java -version >>>>>>> and javac >>>>>>> -version. So JVM itself is working, but I think it's trying to >>>>>>> grab too >>>>>>> much memory that the virtual server core won't grant me at one time. >>>>>>> >>>>>>> Has anyone worked this this type of thing? >>>>>>> >>>>>>> Thanks!! >>>>>>> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ0pekrP3NbaWWqE4RAvCwAJ9hnAOfj2Oh4oT9czjQ82/sJ6qaUACdElZQ NoKOUkB5rFefaO7pduJoeaA= =/dQ3 -----END PGP SIGNATURE-----
