Lab server capacity
-
I'm working on playing around and setting up some different things on an old box, with just a dual-core Pentium and 8 GB of RAM.
I'm planning to run Xen off a flash drive and set up RAID with a couple other drives. I'm picturing running VMs for different functions included in the tags, like serving files, building a database and a wiki, a web server for a couple little family sites that get very little traffic, and playing in different OSs.
I'd like to get started with logging too, but my understanding is it would require about half my RAM, so I'm expecting to kick that down the road a little for now. I'm also under the impression a lot of these other functions will be all right with 2 GB or less, or maybe as low as 512 MB in some cases.
Are any of these other functions unrealistic to fit on this same box with all the others? It's a little embarassing bringing this basic nature of question here to you all, and I'm open to any other suggestions too, am looking forward to learning across a pretty broad spectrum with this. Would like to max this project out before moving to real server hardware.
-
ELK or ELG (Graylog2) would definitely eat 4GB+. We use 8GB on ours and it is tight.
-
Let's see if I can come up with a decent run down...
Total Memory 7.5GB (XenServer uses 512MB)
- ownCloud (2GB)
- web server (Apache?) (1GB)
- database server (MariaDB?) (1GB)
- file server (Samba?) (1GB)
- VMS (What's this?)
- Wiki (why isn't this on the web server?)
- AD (Windows 3GB, Linux 1GB)
If I break it down this rough way, that's 6GB with AD on Linux and not enough available memory to really do it on Windows. You can shave a little here and there and just get Windows to fit.
Most of these can be trimmed some. ownCloud could go down to 1.5GB or so. The web server to 800MB and things like that. Little trims that add up.
I have no idea what VMS is here. VMS is an OS and can't run on AMD64 so this must not be what I am thinking.
The wiki is a web application. You have a web server. The wiki should logically be the application on the web server, no? So that would not use its own memory, it's part of the web server, right?
-
Perfect, thanks Scott.
The VMs are just virtual machines to play with different distros
-
--
-
@ryanblahnik said in Lab server capacity:
Perfect, thanks Scott.
The VMs are just virtual machines to play with different distros
Oh, VMs, not VMS? Ha ha. With the capital S it never occurred to me that you might mean plural VM.
-
@ryanblahnik said in Lab server capacity:
@scottalanmiller Thanks for all the feedback. You're obviously right about the wiki too.
Instead of squeezing everything in to make enough room for AD, my next reaction would be to probably just push that off with logging to next time. Leave everything with its recommended memory and have a little room to play around with a few things, blow them up and try others.
If you use Samba4 for your AD, you have plenty of overhead. It's just Windows with a GUI that would cause it to be really tight.
-
Hmm, just having that DC on there would probably be enough to play with. I've got a couple old and mostly functioning Windows laptops here I can tie in for testing. Windows without the GUI might be better than nothing too.
-
@scottalanmiller said in Lab server capacity:
- ownCloud (2GB)
I run ownCloud with 1024 in production. I have installed for testing processes on 512.
-
@scottalanmiller It took me a minute to realize again where you were seeing that haha, I switched that tag out
-
@JaredBusch said in Lab server capacity:
@scottalanmiller said in Lab server capacity:
- ownCloud (2GB)
I run ownCloud with 1024 in production. I have installed for testing processes on 512.
Good to know, I've not done capacity testing with it and only knew that 2GB was plenty.
-
Getting lots of eyes on this thread today. Very interesting.
