Major Description
when running oak with additional immutable mounts, the permission provider will come with a composite MountPermissionStore that loads entries from the different mount points.
while for the mutable default mount reading the latest permission data from the NodeStore is required whenever the cache gets invalidated, this is probably not needed for immutable mounts.
the goal of the this improvement is to investigate if and under which circumstances repeated reads for the immutable mounts can/should be prevented and measure the impact on overall performance. this includes taking potentially huge amounts of permission entries into account and define boundaries in case such an improvement was beneficial for mounts with relatively few permissions.
Attachments
Attachments
1.
|
Create permission-evaluation specific benchmarks with mounts |
|
Open | Unassigned |
2.
|
Benchmark results for Status Quo |
|
Open | Unassigned |
3.
|
Benchmark results for potential improvements |
|
Open | Unassigned |