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

Perfomance: Add index for url_path #100

Open
Alexnortung opened this issue Jan 23, 2024 · 4 comments
Open

Perfomance: Add index for url_path #100

Alexnortung opened this issue Jan 23, 2024 · 4 comments
Labels
enhancement New feature or request Needs investigation This needs some diving in to before it can be worked on

Comments

@Alexnortung
Copy link
Collaborator

Feature request

Summary

I think the url_path field needs a database index, such that finding a url alias by it's path will be faster.

Suggested solution(s)

Take a look at the strapi repo code (or here) for an example.

@boazpoolman
Copy link
Member

Is this feature documented somewhere?

@boazpoolman boazpoolman added enhancement New feature or request Needs investigation This needs some diving in to before it can be worked on labels Jan 23, 2024
@Alexnortung
Copy link
Collaborator Author

I guess it is an experimental feature, I don't think it is documented anywhere other than on their feedback page. I have noticed it multiple times when looking around in some of the strapi source code.

@boazpoolman
Copy link
Member

Interesting. Are you currently having performance issues without the index?

@Alexnortung
Copy link
Collaborator Author

I have had some performance issues while building static pages for our frontend when we have 100s of pages, but I am not sure whether adding an index to url alias would be noticable anyway. My guess is that it could have some impact, since I use /webtools/router for each page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Needs investigation This needs some diving in to before it can be worked on
Projects
None yet
Development

No branches or pull requests

2 participants