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
That is certainly possible and should not affect the outcome of a profile validation, so having the tree "cached" locally would certainly speed up processing. And since we expect (and encourage) users to build profiles on top of existing ones, this use case is going to become more frequent.
We can probably leverage the code from the Mockup Creator to store a cache copy for processing.
I was under the impression that this decorator would cache the last calls of this function for later, but maybe this behavior isn't checking out with changes to the program. If it is, it should be caching the responses for each resource based on the URI provided.
edit: It's very possible that the cache limit is too low for many services, especially since you can easily have 128 log entries and the cache will remove the earlier calls, defeating the purpose of the cache. If you are able to test bumping this up to a much higher number, it might work at expense of memory allocation.
Also wondering if stacking the profiles together before validation is more accurate to the spec than validating each profile individually.
Uncovered by @JordanCHW: When validating multiple profiles, the current implementation does ValidateURITree for each profile.
Redfish-Interop-Validator/RedfishInteropValidator.py
Lines 196 to 215 in 2ed5dd2
This can slow down the test significantly given that for N profiles, we do N treecrawls to validate all profiles.
Can the implementation instead take a snapshot of the redfish tree prior to ValidateURITree and use the same snapshot for validating all profiles?
The text was updated successfully, but these errors were encountered: