Nginx VM
-
What is the best method to determine the disk size for a Nginx reverse proxy? I plan on having a minimal amout of servers behind it. ie: Nextcloud, Bookstack, and Unifi Controller. I have searched and cannot find any concrete info on how big to make the disk for the VM or how much resources to give it. This is my first attempt at setting all of this up behind a proxy.
-
@brandon220 said in Nginx VM:
What is the best method to determine the disk size for a Nginx reverse proxy? I plan on having a minimal amout of servers behind it. ie: Nextcloud, Bookstack, and Unifi Controller. I have searched and cannot find any concrete info on how big to make the disk for the VM or how much resources to give it. This is my first attempt at setting all of this up behind a proxy.
Assuming you are installing minimal install of Fedora.
I prefer to use 20 GB. -
@black3dynamite Yes. Minimal. I could not find anything that gave a "best practice" on what size disk was needed. I would have been guessing honestly. What about ram?
-
@brandon220 said in Nginx VM:
@black3dynamite Yes. Minimal. I could not find anything that gave a "best practice" on what size disk was needed. I would have been guessing honestly. What about ram?
I have a max allocation of 2GB.
-
So pretty much my minimal starting point is 20GB storage, 2GB RAM and 1 vCPU.
-
My Nginx proxy on Vultr runs on 512MB RAM no problem. Minimal install.
-
@brandon220 said in Nginx VM:
@black3dynamite Yes. Minimal. I could not find anything that gave a "best practice" on what size disk was needed. I would have been guessing honestly. What about ram?
There isn't one. NGinx just needs a few MB over the base OS. The base OS will account for 99.99% of the disk usage, and Nginx for a trivially small additional amount. You won't even really notice.
Our Fedora 29 Nginx box uses about 3.3GB of disk. If you used only 4GB, you'd be fine. But why cut it so close in this day and age?
-
My Nginx proxy on Vultr runs on 512MB RAM no problem. Minimal install.
It's faster if you have more. It'll cache. Here is a unit with excess RAM. I would give 1GB if you have it. Maybe not on cloud, but in a VM...
# free -m total used free shared buff/cache available Mem: 3942 392 2038 1 1511 3304 Swap: 1335 0 1335
-
@black3dynamite said in Nginx VM:
So pretty much my minimal starting point is 20GB storage, 2GB RAM and 1 vCPU.
That's what we do. 24GB of storage thin provisioned.
-
@brandon220 said in Nginx VM:
@black3dynamite Yes. Minimal. I could not find anything that gave a "best practice" on what size disk was needed. I would have been guessing honestly. What about ram?
512MB will work. 1GB is better. 2GB is ideal.
-
I think the worst part about running with 512MB is installing Fedora. That was painful, even in text mode.
-
-
@scottalanmiller said in Nginx VM:
I think the worst part about running with 512MB is installing Fedora. That was painful, even in text mode.
Really? Been a while since I did it with that little RAM, but I do from time to time and don't remember it being any different.
Idk if it was just the process on Vultr with the custom ISO, or what, but it was bad. I think the last time I did it was Fedora 27, so it's definitely been a while.
-
@scottalanmiller said in Nginx VM:
I think the worst part about running with 512MB is installing Fedora. That was painful, even in text mode.
Really? Been a while since I did it with that little RAM, but I do from time to time and don't remember it being any different.
Idk if it was just the process on Vultr with the custom ISO, or what, but it was bad. I think the last time I did it was Fedora 27, so it's definitely been a while.
Oh, custom ISO. Maybe I've not tried that in a few versions.
-
@scottalanmiller said in Nginx VM:
@scottalanmiller said in Nginx VM:
I think the worst part about running with 512MB is installing Fedora. That was painful, even in text mode.
Really? Been a while since I did it with that little RAM, but I do from time to time and don't remember it being any different.
Idk if it was just the process on Vultr with the custom ISO, or what, but it was bad. I think the last time I did it was Fedora 27, so it's definitely been a while.
Oh, custom ISO. Maybe I've not tried that in a few versions.
That's the only way to get true minimal right?
-
Thanks for the info. I normally use 2G of ram and 2vCPU on most Fedora installs. I will give it a go. I was mostly unsure of how much resources were used between the proxy and the back-end server. Seems like it would be more but that is why I'm asking.
-
@brandon220 said in Nginx VM:
I normally use 2G of ram and 2vCPU on most Fedora installs.
That's a lot. We use 1 vCPU for most installs, even in production. 2GB of RAM if you have lots of spare, maybe. But might be a little high for all systems.
-
@scottalanmiller said in Nginx VM:
@scottalanmiller said in Nginx VM:
I think the worst part about running with 512MB is installing Fedora. That was painful, even in text mode.
Really? Been a while since I did it with that little RAM, but I do from time to time and don't remember it being any different.
Idk if it was just the process on Vultr with the custom ISO, or what, but it was bad. I think the last time I did it was Fedora 27, so it's definitely been a while.
Oh, custom ISO. Maybe I've not tried that in a few versions.
That's the only way to get true minimal right?
Correct. The only way to get a true "anything" that isn't the cloud hosts' custom install.
-
@scottalanmiller Ok. I'll try scaling back a bit and see how it goes.
-
@scottalanmiller said in Nginx VM:
@scottalanmiller said in Nginx VM:
I think the worst part about running with 512MB is installing Fedora. That was painful, even in text mode.
Really? Been a while since I did it with that little RAM, but I do from time to time and don't remember it being any different.
Idk if it was just the process on Vultr with the custom ISO, or what, but it was bad. I think the last time I did it was Fedora 27, so it's definitely been a while.
Oh, custom ISO. Maybe I've not tried that in a few versions.
Yes, using the ISO (any) of fedora 28+ is slower than hell on 512 RAM.