Deployment jumped up memory by 10% - Forge

Hey!

Can anybody offer any advise on monitoring memory/find out where the memory is being used on Digital Ocean Droplets provisioned by Forge?

I've just ran a deployment with a few changes, not many additions and my CPU jumped up from 3 to 25% and then went back down and my memory went from a steady 53% to a slow creeping up 65% now.

I originally way over provisioned this setup by having a 4 server setup, 2 application servers (one was for api.domain.com and the other the main webapp domain.com), a redis server and DB server following a tutorial on server for hackers.

This worked great but was more for fun learning how to do it so I removed two of the droplets leaving only one application droplet and a DB droplet. This caused an issue at the time, I believe due to firewall rules as the remaining servers were trying to connect to servers that no longer existed but a restart seemed to fix this issue.

Firstly I now have 3 Laravel apps on a single 2GB memory, 2 vCPUs and 3TB transfer droplet (app/api/docs). I'm thinking this is a bit too much?

Doing free -m I get the following:

              total        used        free      shared  buff/cache   available
Mem:           1993         958         101          28         934         825
Swap:          1023          41         982

Secondly has anyone any ideas on why my memory might now be creeping after after a single, not substantial deployment?

Sorry this is a bit wordy! Thought I would add as much info as I have.

Thanks!