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

Only available applications slowdown #18

Open
iLLiCiTiT opened this issue Aug 20, 2024 · 2 comments
Open

Only available applications slowdown #18

iLLiCiTiT opened this issue Aug 20, 2024 · 2 comments

Comments

@iLLiCiTiT
Copy link
Member

iLLiCiTiT commented Aug 20, 2024

Current Behavior

When Only available applications is checked (ayon+settings://applications/only_available), discovering of applications is a lot slower in launcher tool. Don't know why but it may slow down discovery by seconds.

@BigRoy
Copy link
Contributor

BigRoy commented Aug 20, 2024

It's likely because it checks for the existence of the executables for each application, on each task change. We may want to:

  • cache the results of the check unless a user hard-refreshes?
  • see if we can optimize the existing check on disk somehow?

However, it even feels slow for the amount of applications. It shouldn't be that slow to just check whether e.g. 200 files exist or not. Maybe each entry application executable may format via Anatomy that gets re-initialized each time.. but that's a wild guess.

@BigRoy
Copy link
Contributor

BigRoy commented Sep 17, 2024

Just cross-referencing. This came up on discord just now here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants