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

When loading from a repository that has a very large framework, takes a lot longer than desired. #12

Open
Lomilar opened this issue Feb 1, 2019 · 2 comments

Comments

@Lomilar
Copy link
Member

Lomilar commented Feb 1, 2019

Dev has a framework on it that makes the initial load of frameworks take 90+ seconds.

The "open framework" lookahead should use search capabilities (<searchphrase>*) instead of doing word matching and preloading all the frameworks.

@whistlinjoe
Copy link
Collaborator

whistlinjoe commented Feb 1, 2019

@Lomilar I can do this but I think it would also be wise to add a new search mechanism for the EC objects. Response time for performing a simple query for all frameworks in a repository should not be dependent on how many relations/sub components a framework has. It shouldn't take that long until your record count is in the millions.

Something like EcFramework.searchSimple that returns the Id, Name, Description, and Owner. We shouldn't need to increase the complexity of UIs to account for things in the library.

@Lomilar
Copy link
Member Author

Lomilar commented Feb 1, 2019

image

In the above picture, 1.4 minutes were spent on the server, 3 seconds on the download.

Much of the time is spent by the server doing security scans of the object to ensure there is no encrypted data that needs to be stripped out, not transmitting the data. The scan needs to be across the entire object anyway, as recent security protocols now omit an object if it includes any encrypted data that the requesting party is not allowed to see. I expect this is what is so slow.

We may want to kick this over to Skyrepo to optimize that process.

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