-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR: Unknown user-defined format specifier "pss". #8
Comments
FWIW here is my initializer: PumaAutoTune.config do |config|
config.ram = Integer(ENV['AVAILABLE_MEMORY'] || 768) * 0.98 # memory * percent utilization
# Set our max_workers to what is in the ENV var + 1 because
# PumaAutoTune uses new worker count < max_workers. That means
# w/out adding 1 with a PUMA_MAX_WORKERS of 5 we would only
# ever actually run 4... seems counter-intuitive so +1.
config.max_workers = Integer(ENV['PUMA_MAX_WORKERS'] || 3) + 1
end
PumaAutoTune.start |
Relevant Heroku config:
|
Further digging implicates the get_process_mem gem even more so I will open an issue there and reference this one. Running a bash shell on Heroku and trying to run what it looks like get_process_mem would run from there results in the exact output I see in my web dyno logs above:
|
I've updated |
This looks like it could be related to #2 #3 and #6 but I'm not positive.
It also seems like it may be related to the v1.0 updates in your get_process_mem gem?
Below is the log from Heroku for one of my web dynos shortly after updating from puma_worker_killer to puma_auto_tune (which included an update to get_process_mem along the way). Things started out OK until I hit a heavy page. As you can see below, I hit a few R14 memory errors (padding added around them so they stand out). The logs also include the output of log-runtime-metrics.
The memory usage reported by PumaAutoTune does not seem to match what is reported by log-runtime-metrics. The first time the R14 comes up, lrm reports 554M in use whereas the PAT stats around there report < 500M in use.
I have PAT configured with
config.ram = Integer(ENV['AVAILABLE_MEMORY'] || 768) * 0.98
andENV['AVAILABLE_MEMORY']
is set to 512.Eventually, after 2x R14 errors, PAT detects the over memory condition. At that point it freaks the hell out dumping a ton of log entries stating that it's resizing to remove a worker and current_cluster_size=2. This goes on for quite a bit during which period we see two additional R14 errors.
Eventually towards the bottom is where things get REALLY interesting as we see
2014-04-03T22:57:03.602261+00:00 app[web.2]: ERROR: Unknown user-defined format specifier "pss".
followed by what looks like help output for a linux command. That's what made me think of the changes to get_process_mem...The text was updated successfully, but these errors were encountered: