From e2207e5cd196248e3cc7cc8f9a29c6debc22f051 Mon Sep 17 00:00:00 2001 From: ZL Deng Date: Thu, 21 Apr 2022 17:42:56 +0200 Subject: [PATCH] fixed #13, update readme --- README.md | 7 +- ribodetector/__init__.py | 2 +- ribodetector/detect.py | 32 ---- ribodetector/detect_cpu.py | 319 +++++++++++++++++++++++++++++++------ 4 files changed, 271 insertions(+), 89 deletions(-) diff --git a/README.md b/README.md index 9f0d24e..6896e70 100644 --- a/README.md +++ b/README.md @@ -154,13 +154,12 @@ optional arguments: -t THREADS, --threads THREADS number of threads to use. (default: 10) --chunk_size CHUNK_SIZE - chunk_size * threads reads to process per thread.(default: - 1024) - When chunk_size=1024 and threads=20, each process will load - 1024 reads, in total consumming ~20G memory. + chunk_size * 1024 reads to load each time. + When chunk_size=1000 and threads=20, consumming ~20G memory, better to be multiples of the number of threads. -v, --version show program's version number and exit ``` +**Note**: RiboDetector uses multiprocessing with shared memory, thus the memory use of a single process indicated in `htop` or `top` is actually the total memory used by RiboDector. Some job submission system like SGE mis-calculated the total memory use by adding up the memory use of all process. If you see this do not worry it will cause out of memory issue.