search

openaustralia / morph

Take the hassle out of web scraping
https://morph.io
GNU Affero General Public License v3.0
461 stars 74 forks source link

Reduce size of production server when possible #1062

Closed mlandauer closed 8 years ago

mlandauer commented 8 years ago

Once we've done the postgres migration and any other things required to keep disk space under control we should reduce the size of the server again. Otherwise it will end up costing a lot of money each month

henare commented 8 years ago

We'll have to remember to reduce the number of concurrent containers then too. At the moment it's specced to be able to run however many 512MB containers simultaneously.

mlandauer commented 8 years ago

I haven't changed the number of concurrent containers after just upgrading the server, so as long as that remains the case we shouldn't have to change the number of concurrent containers when we downgrade the server

mlandauer commented 8 years ago

I had to resize the disk back down to 392,960 MB (= 768GB / 2 - 256 MB), then migrate to the smaller plan which took about half an hour for each operation. Now, after the move to the smaller disk we are now at 54% full. Pretty good!

This was obviously only possible after doing a bunch of work to clear disk space before the migration back to the small production server