Ive been trying to push some changes to the gateway but ive been getting consistent time-out errors. The memory on the gateway seems to be fine, but the errors persist and is not letting me update changes. Could running ignition on a vm running an emulator simaltaneously be a possible cause?
The clock drift errors may be a red herring, as they are barely tripping the 1000ms boundary. Consider setting a max GC pause target of 100ms in ignition.conf--your drift reports may go away.
You should examine your gateway log for server errors that correspond to your attempts to save changes. Timeouts that don't correspond to memory or CPU spikes are often side effects of errors in the gateway. If you find something suspicious, post the backtrace here (with code formatting).
Nothing in the logs except for timeouts.