-
Notifications
You must be signed in to change notification settings - Fork 157
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
Performance and Error Issues with VEP v111 Docker Container #1681
Comments
Hi Ananya, Hope you are having a nice day. Sorry for the inconvenience. Could you show the command that you are using to run VEP? Thank you. Cheers, |
Hi Nuno, Thank you for your response. We conducted testing using ARGO.
VEP Version Used: 111 & 109.3 Considering our dependency on AKS and ARGO, our capabilities are constrained to effectively utilizing 5 vCPUs and 25 GB of RAM for configurations with 8 vCPUs and 32 GB RAM, and 13 vCPUs and 55 GB of RAM for configurations with 16 vCPUs and 64 GB RAM. Here is the command we are using to run VEP:
In addition, we utilized nine custom files and the plugins pLI, CADD, and dbscSNV, for our annotation. We encountered the same error with VEP versions 109.3 and 111, whereas VEP version 106.1 completed the annotation in 7 minutes for the same file. Looking forward to your assistance. Thank you. Best regards, |
Hi @Ananya-swi, Thanks for sending more information. You seem to be using VEP as expected, so I am not really sure why it is taking so much time. Some ideas/questions about the performance issues:
Looking forward to your reply. Best, |
Hi @nuno-agostinho , Thanks for your response. I've tried the method you suggested, removing the plugins, but I am still encountering the same issue. When I use
Explanation of Using I used the VEP command without the --buffer_size flag. Here is the command:
Using
Despite following the suggestions, the issue persists. The script runs with a smaller buffer size but takes a significantly longer time to complete. It appears that higher buffer sizes and fork counts lead to process communication issues. I tried these commands with VEP versions 111 and 109.3, and the same error occurs. However, when using versions 106.0 or 106.1, it works without any issues. Could you provide further insights or additional configurations that might help resolve this problem? I look forward to your guidance on this issue. Thanks, |
Hi,
We are currently using the VEP v111 Docker container to annotate VCF files. However, we are facing the following issues:
Previously we were using v106.1. Which is taking only 7 minutes to complete the same file. We also tried with v109.3, which leads to same error.
We would appreciate any guidance or suggestions to resolve these issues. Looking forward to your reply. Thank you in advance for your assistance.
Regards,
Ananya Saji
Data Engineer (Bioinformatics)
Semantic Web Tech Pvt. Ltd.
The text was updated successfully, but these errors were encountered: