Re^3: Multithreads with an executable in the worker subroutine

Copying the entire database for each thread is about 500MB of space per thread, but it seems to be working. There is definitely some kind of block, after seeing this.

However, I don't think it is a system block because I was able to put 4 blast queries into a loop in the bash shell and fork them, and top showed all four running at the same time.

Comment on Re^3: Multithreads with an executable in the worker subroutine

Replies are listed 'Best First'.
Re^4: Multithreads with an executable in the worker subroutine by BrowserUk (Patriarch) on May 31, 2012 at 17:41 UTC
However, I don't think it is a system block because I was able to put 4 blast queries into a loop in the bash shell and fork them, and top showed all four running at the same time. That really doesn't make any sense at all. When you spawn blast from several threads, the blast instances are running as separate processes, so should be completely unaffected by anything in the parent process, regardless of whether it is using threads or not. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. The start of some sanity?	[reply]
Re^4: Multithreads with an executable in the worker subroutine by bulk88 (Priest) on May 31, 2012 at 21:04 UTC
500 MB? Have you looked at the hard drive light? I suggest a memory mapped read only file shared among processes or threads if read-only mode can work for you.	[reply]