Closed wincent closed 8 years ago
Or, perhaps better still, as Amjad suggests, I could just increase swap size. Beware the gotchas mentioned in that thread, though, and those listed here. Of those, about the only one that really concerns me is the possibility of excessive charges if a process were to go rogue and thrash the swap all month without me noticing.
Went with swap. Made a gig of it. Was able to deploy on first try:
status running
monitoring status monitored
load average [0.75] [0.30] [0.14]
cpu 78.2%us 8.9%sy 10.8%wa
memory usage 180972 kB [17.7%]
swap usage 40 kB [0.0%]
data collected Fri May 6 07:35:10 2016
Barely using swap (40 kB).
These t2.micro instances sure are cheap, but webpack builds often fail due to OOM errors, requiring me to (at least) stop the wikiserve service and (sometimes even) masochist itself, which means the site 502's during deployments.
So, might have to avoid doing the build remotely; instead do it locally, commit the result to a
build
branch and push that directly. One nice thing about that is that it will make deployments super fast.