Bug #16813
closed
User batch updates should avoid useless work
Description
Don't update user records (or recompute permissions) if nothing has changed.
Reported that each user record being updated would trigger a full materialized permission view update. Arvados 2.1 incremental permission updates should be an improvement, but we still want to avoid triggering a redundant refresh of each individual user's permissions.
Updated by Tom Clegg over 3 years ago
16813-avoid-noop-user-updates @ 98bd6c43fca91b76d528c8ed5b83c655c86ffe3c -- developer-run-tests: #2088
Updated by Peter Amstutz over 3 years ago
Tom Clegg wrote:
16813-avoid-noop-user-updates @ 98bd6c43fca91b76d528c8ed5b83c655c86ffe3c -- developer-run-tests: #2088
The initial load of the user list could be done in a single query instead of loading each user record individually. But that's not a bottleneck we set out to fix in this branch, so just something to consider for future optimization.
LGTM.
Updated by Peter Amstutz over 3 years ago
- Status changed from New to In Progress
Updated by Anonymous over 3 years ago
- Status changed from In Progress to Resolved
Applied in changeset arvados|62f82658619bd59644b4bdac6b83be8fe87aca0d.