Geo log cursor reported to use lots of RAM
Per https://gitlab.com/gitlab-org/gitlab-ee/issues/3999#note_46983471
@grzesiek was that the startup cost, or is this after a period of running? Since this is a Ruby daemon, I suppose we can expect it to grow a bit over time.
Do we need to implement a maxrss-killer for it?
Running locally, I see:
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
lupine 23056 0.0 0.9 728204 324132 pts/1 Sl+ Nov08 5:58 ruby ./geo_log_cursor
~320MiB RSS is about what I was expecting - Ruby is hangry