The runtime for a job usually increase with an increase in the following:
1. Size of the query structure.
2. Size of database.
3. Number of representative atoms.
4. Number of best matched cliques for each alignment.
Note: The reported run times were calculated when the
system was idle (no other resource intensive operation was running on the
system). The run time may vary for a new database search depending on the system load and rank of your job in the
queue. If the job is in queue then the waiting time in the queue will be added to the standard runtime of the job.
Approximate runtime estimate for searching 'Protein database' (24,563 PDB chains, NR 90) |
PDB Code
|
Size
|
Runtime in hours
|
5CFH
|
100 residues
|
13 hours
|
1A3H
|
300 residues
|
13 hours
|
5EJY
|
500 residues
|
18.5 hours
|
Approximate runtime estimate for searching 'Human Protein database' (3468 PDB chains, NR 90) |
PDB Code
|
Size
|
Runtime in hours
|
5CFH
|
100 residues
|
1.5 hours
|
1A3H
|
300 residues
|
2.5 hours
|
5EJY
|
500 residues
|
3 hours
|
Approximate runtime estimate for searching 'DNA Protein complex' database (2262 PDB) |
PDB Code
|
Size
|
Runtime in hours
|
1AN2
|
86 residues
|
1 hour 7 minutes
|
4Z6C
|
335 residues
|
1 hour 20 minutes
|
5D9Y
|
462 residues
|
1 hour 45 minutes
|
Approximate runtime estimate for searching 'RNA' database (493 PDB, NR 90) |
PDB Code
|
Size
|
Runtime in hours
|
5KVJ
|
32 residues
|
15 minutes
|
3RGJ
|
172 residues
|
17 minutes
|