Skip to content

perf: reduce per-assignment Casbin calls in visible assignments fast path#278

Draft
mariajgrimaldi wants to merge 2 commits intomainfrom
MJG/perf-visible-assignments
Draft

perf: reduce per-assignment Casbin calls in visible assignments fast path#278
mariajgrimaldi wants to merge 2 commits intomainfrom
MJG/perf-visible-assignments

Conversation

@mariajgrimaldi
Copy link
Copy Markdown
Member

Description

Three changes to cut latency in get_visible_role_assignments_for_user:

  1. Pre-filter by org/scope/role before the authorization pass so Casbin never evaluates assignments that would be filtered out anyway.

  2. Replace the per-assignment enforcer.enforce() loop in _filter_allowed_assignments with a single batch_enforce() call.

  3. Memoize get_permissions_for_single_role within get_role_assignments so the same role key is not expanded multiple times in one call.

Merge checklist:
Check off if complete or not applicable:

  • Version bumped
  • Changelog record added
  • Documentation updated (not only docstrings)
  • Fixup commits are squashed away
  • Unit tests added/updated
  • Manual testing instructions provided
  • Noted any: Concerns, dependencies, migration issues, deadlines, tickets

…path

Three changes to cut latency in get_visible_role_assignments_for_user:

1. Pre-filter by org/scope/role before the authorization pass so Casbin
   never evaluates assignments that would be filtered out anyway.

2. Replace the per-assignment enforcer.enforce() loop in
   _filter_allowed_assignments with a single batch_enforce() call.

3. Memoize get_permissions_for_single_role within get_role_assignments
   so the same role key is not expanded multiple times in one call.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@openedx-webhooks openedx-webhooks added open-source-contribution PR author is not from Axim or 2U core contributor PR author is a Core Contributor (who may or may not have write access to this repo). labels May 7, 2026
@openedx-webhooks
Copy link
Copy Markdown

Thanks for the pull request, @mariajgrimaldi!

This repository is currently maintained by @openedx/committers-openedx-authz.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

  • If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
    • This process (including the steps you'll need to take) is documented here.
  • If it doesn't, simply proceed with the next step.
🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

  • Dependencies

    This PR must be merged before / after / at the same time as ...

  • Blockers

    This PR is waiting for OEP-1234 to be accepted.

  • Timeline information

    This PR must be merged by XX date because ...

  • Partner information

    This is for a course on edx.org.

  • Supporting documentation
  • Relevant Open edX discussion forum threads
🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

🔘 Update the status of your PR

Your PR is currently marked as a draft. After completing the steps above, update its status by clicking "Ready for Review", or removing "WIP" from the title, as appropriate.


Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

  • The size and impact of the changes that it introduces
  • The need for product review
  • Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

… assignments

Bypass Casbin enforce() entirely in _filter_allowed_assignments:
- Check staff/superuser once via Django User query (early return)
- Call get_scopes_for_subject_and_permission once per distinct permission
  type (typically 1-2 calls total) instead of N enforce() calls
- Filter in Python using key_match_func for glob scope support

This eliminates the is_admin_or_superuser_check overhead (ScopeData/UserData
construction per item, RequestCache lookups) that dominated the previous
batch_enforce path.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

core contributor PR author is a Core Contributor (who may or may not have write access to this repo). open-source-contribution PR author is not from Axim or 2U

Projects

Status: Needs Triage

Development

Successfully merging this pull request may close these issues.

2 participants