You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The openactive gem allocates a large amount of objects on require. Roughly 3MB, which might not sound like a lot, but we were routinely being pushed only a few MB over our heroku dyno's limit.
These are the gems that allocate the most memory in our app, found using the derailed_benchmarks gem:
As you can see the openactive gem allocates an outsized amount of memory compared to other gems (the dead_end gem is a dependency of the profiler, so isn't in the production app).
From what I can see this memory is mostly strings, the strings used in the define_property calls, exacerbated by the fact that the JsonLdSerializable concern appears to clone all the properties so will double the allocations. You can see this from the memory allocations by file here:
This is only the first few lines of the output, there's a lot more files from openactive further down, but each one contributes only a small amount to the total memory allocations.
The text was updated successfully, but these errors were encountered:
With thanks to @rsslldnphy for this report:
The openactive gem allocates a large amount of objects on require. Roughly 3MB, which might not sound like a lot, but we were routinely being pushed only a few MB over our heroku dyno's limit.
These are the gems that allocate the most memory in our app, found using the
derailed_benchmarks
gem:As you can see the openactive gem allocates an outsized amount of memory compared to other gems (the
dead_end
gem is a dependency of the profiler, so isn't in the production app).From what I can see this memory is mostly strings, the strings used in the
define_property
calls, exacerbated by the fact that theJsonLdSerializable
concern appears to clone all the properties so will double the allocations. You can see this from the memory allocations by file here:This is only the first few lines of the output, there's a lot more files from openactive further down, but each one contributes only a small amount to the total memory allocations.
The text was updated successfully, but these errors were encountered: