Bug #16813

User batch updates should avoid useless work

Added by Peter Amstutz about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
API
Target version:
Start date:
09/11/2020
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Story points:
-
Release relationship:
Auto

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.


Subtasks

Task #16820: Review 16813-avoid-noop-user-updatesResolvedPeter Amstutz

Associated revisions

Revision 62f82658
Added by Tom Clegg about 1 year ago

Merge branch '16813-avoid-noop-user-updates'

fixes #16813

Arvados-DCO-1.1-Signed-off-by: Tom Clegg <>

History

#1 Updated by Peter Amstutz about 1 year ago

  • Description updated (diff)

#2 Updated by Peter Amstutz about 1 year ago

  • Assigned To set to Tom Clegg

#3 Updated by Peter Amstutz about 1 year ago

  • Release set to 25

#4 Updated by Peter Amstutz about 1 year ago

  • Description updated (diff)

#5 Updated by Peter Amstutz about 1 year ago

  • Category set to API

#7 Updated by Peter Amstutz about 1 year ago

Tom Clegg wrote:

16813-avoid-noop-user-updates @ 98bd6c43fca91b76d528c8ed5b83c655c86ffe3c -- https://ci.arvados.org/view/Developer/job/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.

#8 Updated by Peter Amstutz about 1 year ago

  • Status changed from New to In Progress

#9 Updated by Anonymous about 1 year ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF