Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Evaluate providing some built-in ORM caching #121

Open
Kircheneer opened this issue May 23, 2023 · 2 comments
Open

Evaluate providing some built-in ORM caching #121

Kircheneer opened this issue May 23, 2023 · 2 comments
Labels
status: gathering feedback Further discussion is needed to determine this issue's scope and/or implementation type: feature Introduction of substantial new functionality to the application

Comments

@Kircheneer
Copy link
Contributor

Kircheneer commented May 23, 2023

Environment

  • Nautobot version: latest
  • nautobot-ssot version: latest

Proposed Functionality

Have the framework expose something like get_from_cache(content_type, **kwargs) with a cache scoped to the execution of a single job.

Use Case

Objects that are commonly looked up (e.g. Region, Status) could be looked up from the DB once in the beginning and then, for CRUD operations on models or during loading, just be looked up from memory, speeding up operations as a whole.

@Kircheneer Kircheneer added status: gathering feedback Further discussion is needed to determine this issue's scope and/or implementation type: minor feature labels May 23, 2023
@lampwins
Copy link
Member

Yes, this is very much needed as it is a pattern that is commonly implemented by developers today in ssot jobs.

@Kircheneer
Copy link
Contributor Author

This is implemented as of #296 but needs to be exposed in documentation still.

@smk4664 smk4664 added type: feature Introduction of substantial new functionality to the application and removed type: minor feature labels Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: gathering feedback Further discussion is needed to determine this issue's scope and/or implementation type: feature Introduction of substantial new functionality to the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants