Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use of local CPU resources #10

Open
vpbrendel opened this issue Feb 16, 2016 · 2 comments
Open

use of local CPU resources #10

vpbrendel opened this issue Feb 16, 2016 · 2 comments

Comments

@vpbrendel
Copy link
Member

The current setup does not use the full power of the local (VM) resources. In particular, GeneSeqer is always run in non-parallel mode, even on a VM with multiple processors.

Performance gains should be substantial by allowing the user an additional parameter when setting the Transcript Spliced Alignment options: "Number of processors". If set to a number >1 [default can be 1],
then the script splitMakearryGSQ.pl (could be renamed in the process!) could be asked to invoke GeneSeqerMPI instead of GeneSeqer.

Suggestion: assign parameter passing to Jon, GeneSeqerMPI implementation to Volker, independent testing to Daniel

Priority: not urgent, but attractive

@standage
Copy link
Member

Some sanity checking would be in order of course. If I were to test this feature, I would see how xGDBvm GUI handles the following as input.

  • 1
  • n (number of CPUs on the system)
  • 4_n_
  • 999999
  • -1
  • reuben

It should be possible to programmatically probe the number of CPUs on the VM (/etc/procinfo?) and to make sure the number of requested processors does not exceed the number of available CPUs.

@vpbrendel
Copy link
Member Author

Simple check in the script, using the following variable setting (echo included for your testing on your VM):

np=cat /proc/cpuinfo | grep processor | wc -l; echo $np

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants