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
In the theoretical event that one or many response files are huge, we would be bloating memory by loading them each into a template and holding them in memory until access.
adding something like skip_cache: true to the yaml would cause the response templates to not be stored in memory between calls and instead loaded each time the route is called. This would cause the memory jumps to be short spikes rather than sustained load, which would be especially beneficial for many very large response files.
The text was updated successfully, but these errors were encountered:
In the theoretical event that one or many response files are huge, we would be bloating memory by loading them each into a template and holding them in memory until access.
adding something like
skip_cache: true
to the yaml would cause the response templates to not be stored in memory between calls and instead loaded each time the route is called. This would cause the memory jumps to be short spikes rather than sustained load, which would be especially beneficial for many very large response files.The text was updated successfully, but these errors were encountered: