Mercurial > repos > iuc > gecko

comparison README.md @ 0:09459f6ffe08 draft

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
"planemo upload for repository https://github.com/galaxyproject/tools-iuc/tree/master/tools/gecko commit f0c70444d9781900f0af1638792818543c65acfc"
author iuc
date Fri, 27 Nov 2020 14:46:27 +0000
parents
children 5efbd15675ca
comparison
equal deleted inserted replaced
-1:000000000000 0:09459f6ffe08
1 # IMPORTANT INFORMATION FOR SYSTEM ADMINISTRATORS
2
3 The tool GECKO is disk-intensive. This means that the algorithm will write a lot to the hard disk drive, which, even though buffered, can affect the performance of other processes that are sharing the same filesystem by starving their access to the disk.
4
5 ## Recommended use in concurrent systems
6
7 If GECKO is being used concurrently, it is recommended that the input file size is limited in order to avoid overall deterioration of the performance of the system. See details below for an estimate.
8
9 ## Details
10
11 The most disk-consuming step is the writing of "seeds" or "hits". These depend on the length and the similarity of the input sequences.
12
13 - A regular bacterial comparison (1 to 10 MB input sequences) can write around 1 to 5 GB.
14 - A medium-sized comparison (around 20 or 30 MB input sequences) can write around 10 GB.
15 - A chromosome comparison (50 to 200 MB input sequences) between human and gorilla can write around 600 GB. Other "less" similar comparison can write around 100 GB or less.
16