Actually, quite complicated. I use concurrency in different situations:
Firstly, in order to take advantage of multi processor (I have a 12-core workstation), I want to run multiple programs (actually, NCBI blast) at one time. Currently, I solve this by create several perl threads, and run one program in each thread. It works well.
In another situation, I'm making a large ugly GUI program (uses Gtk2), and I want the GUI keep active while background work is running. However, there are some complexed data structure that need to be accessed by both the GUI and worker thread, so I really wants a "real" thread that shares everything by default, but not copying.
In reply to Re^4: issue of concurrency: which module is better
by llancet
in thread issue of concurrency: which module is better
by llancet
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |