| Why KoriBlast seems slow when using NCBI or EBI facility ? |
|
Blasting your sequences or retrieving sequence data (features, taxonomy, etc) may appear to be slow. Actually, it is not the case: KoriBlast just respects the NCBI recommandations for the use of their resources. These are: it is forbidden to query the NCBI faster than one query every 3 seconds to fetch sequence data, and one query every 60 seconds to start a Blast job. In addition, NCBI recommands to wait for the end of one Blast search before sending the next one. KoriBlast uses the same rules when using the EBI resources. As a consequence of the respect of these rules, you will never be blacklisted when using KoriBlast along with the NCBI/EBI services. Even if you have lots of sequences to analyse, KoriBlast will displatch the many jobs during time. Do you want to work faster? Then configure KoriBlast to work locally, as many of our customers, and you'll see the difference.
|