The problem is there is a big price jump to go to 256mb
its 4 times what I am paying now.
What annoys me is that they sell this package with the Webmin as an option when theres no real way its going to work with 64MB ram,
as a newbie to VPS I would not know this. But they should.
I mentioned to them I have more than 1 domain before I signed up and
what I planned on doing with this service.
Looks as if I may just run 1 domain here to get used to using
and controling a VPS and Webmin.
Thanx again for all your help
Shane
Well its after 1am here now so time to get some sleep and try again in the morning
What annoys me is that they sell this package with the Webmin as an option when theres no real way its going to work with 64MB ram,
Webmin is quite different from Virtualmin in its resource requirements. But, Virtualmin (or Webmin) isn’t really where most of the resources are being spent, regardless. Apache is big (depending on modules loaded)…usually much bigger than 64MB. Mail processing requires far more than 64MB. Any one of these services will fit in 64MB, but not all of them…Since Virtualmin is generally used for management of a full hosting stack, it requires a lot of paring down to make it run in a small footprint–it can do it, but the other applications have to be pared back a lot, as well. Without mail or large apps 128MB should be fine (as long as you follow the guide on reducing memory usage, and reduce down to just the services you really need).
It’s easiest for us to just say, “get more memory”, but a lot of folks don’t really need more memory–they just need to adjust their usage down to meet the available memory. Running a single blog, or simple commerce, or whatever, site without email processing is entirely feasible in 128MB. But, as you’ve noted with 64MB “this town aint big enough for the two of us”, where the two would be Virtualmin and just about any other service. The web server is already going to be bumping into that limit.
We do have some plans for a low-memory footprint version of Virtualmin, in the future. Our new VM2 product manages virtualized systems, and realistically, many VPS systems are small. People are shooting for a really low price point with them, and so we need to have some options in place for serving those users. But, it’ll be a while…it requires several tweaks to the current model–we have to figure out what to do about mail, since it can’t be processed locally on a small system, and we have to figure out the webserver problem…nginx or Lighttpd are possibilities, but they have serious limitations vs. Apache and remove a lot of cool Virtualmin functionality (Analytics, some of the proxy options, Subversion, DAV, etc.), and, of course, we have to build a new Webmin module for whichever webserver we choose, which is a very large endeavor.
Looks like I might just have to bite the bullet and go for the 256MB option or find a more affrodable 256mb package, due to my exchange rate to US$ being R8 to $1, I am trying to stay under $15 pm for now.
Have you got any suggesions, looking at around
10 GB Disk Space 256 MB RAM 1Mbps Unmetered Traffic,
the disk space I think is not so critical as I only need around
2 gig or so for my use.
Also regarding the low memory option your working on.
I use a program on my own server to sort my mail so I just use a catch all configuration which sends all email for said domain to me.
This takes the pressure of the web-server, maybe you could suggest a similar setup for use with this package you working on.
Even Windows exchange should be able to handle it.
Well I have just created my first Virtualmin Virtual Servers.
So far so good, memory has ben upgraded to 128 for now and going to see how it goes.
I could not find the setting to stop the libraries from being preloaded in Virtualmin
Also could not find the details that where mentioned in the manual changing of it, so just added "preload_mode=0" to the end of the list that was there in miniserv.conf.
I also follwed the suggestion about reducing the Reduce Apache memory usage