-
Notifications
You must be signed in to change notification settings - Fork 14
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
migrate SSSP export archives #72
Comments
I am going to take another approach here. I work on adding to @sphuber's aiida-sssp package a selector widget with downloading capability: aiidateam/aiida-sssp#25 |
This way we do won't need to import pseudos at the image build/container start-up, but rather do it on-request base. |
That is another possibility. Just keep in mind that this means every app using QE will need to set this up individually. I'm not sure how aiida-sssp does things - we should just make sure that it isn't migrating either. |
The |
Brief update on this issue: With #144 the SSSPs are no longer installed automatically and the QE app is now responsible for installing the SSSPs (aiidalab/aiidalab-qe#25), however like @ltalirz pointed out, since they are not migrated this takes a significant amount of time. |
Are you sure that it is the migration that takes a lot of time and not just the downloading and importing? Anyway, just to point out that you seem to be downloading the |
I am not sure about what exactly takes up the time here, I just know it takes a couple of minutes for the whole process. Just a bit longer than what feels comfortable to me and if we could speed it up somehow, that would be ideal.
Very happy to use utility provided by aiida-pseudo for the QE app instead, whatever works best. Is this related to aiidalab/aiidalab-qe#6 ? |
It is related to that. That was opened against |
By the way, you might get some speedup already from upgrading to aiida 1.5 and benefitting from the improved import/migration code (you can easily test this locally) |
The QE app is now capable of downloading the pseudos, so the issue seems to be resolved. I am going to close it. Feel free to reopen in case you disagree. |
Currently, the SSSP export archives are migrated whenever a new container is started (and this takes time)
Just store the already migrated archives in the image.
The text was updated successfully, but these errors were encountered: