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
Current caching relies on python's built in lru_cache function. When URIs contain fragments (i.e. /redfish/v1/.../Thermal#/Fans/1), it will call the resource /redfish/v1/.../Thermal for each link in a Collection, when once would be satisfactory. Fix could use a wrapper that strips the fragment, then cache that URI.
Consider adding an option for cache size and how much memory it consumes while running the tool on big services.
The text was updated successfully, but these errors were encountered:
Current caching relies on python's built in lru_cache function. When URIs contain fragments (i.e.
/redfish/v1/.../Thermal#/Fans/1
), it will call the resource/redfish/v1/.../Thermal
for each link in a Collection, when once would be satisfactory. Fix could use a wrapper that strips the fragment, then cache that URI.Consider adding an option for cache size and how much memory it consumes while running the tool on big services.
The text was updated successfully, but these errors were encountered: