Skip to main content
Commonmark migration
Source Link

You've hit the RAM bottleneck. Its very common in de novo assemblies and resolved using template assemblies. I don't know this program but suspect it is performing a pairwise analysis for every piece of data in a genomics data set.

The solution is to either:

  1. find a bigger machine, e.g. a big multi-core machine and make sure the program distributes across every core.

    find a bigger machine, e.g. a big multi-core machine and make sure the program distributes across every core.

  2. parallelise the calculation (an excellent way to overcome RAM problems), or,

  3. find an approximation to the calculation that is less computationally demanding, templates are a good way to circumvent this.

  1. parallelise the calculation (an excellent way to overcome RAM problems), or,
  1. find an approximation to the calculation that is less computationally demanding, templates are a good way to circumvent this.

You've hit the RAM bottleneck. Its very common in de novo assemblies and resolved using template assemblies. I don't know this program but suspect it is performing a pairwise analysis for every piece of data in a genomics data set.

The solution is to either:

  1. find a bigger machine, e.g. a big multi-core machine and make sure the program distributes across every core.
  1. parallelise the calculation (an excellent way to overcome RAM problems), or,
  1. find an approximation to the calculation that is less computationally demanding, templates are a good way to circumvent this.

You've hit the RAM bottleneck. Its very common in de novo assemblies and resolved using template assemblies. I don't know this program but suspect it is performing a pairwise analysis for every piece of data in a genomics data set.

The solution is to either:

  1. find a bigger machine, e.g. a big multi-core machine and make sure the program distributes across every core.

  2. parallelise the calculation (an excellent way to overcome RAM problems), or,

  3. find an approximation to the calculation that is less computationally demanding, templates are a good way to circumvent this.

Source Link
M__
  • 13k
  • 5
  • 29
  • 46

You've hit the RAM bottleneck. Its very common in de novo assemblies and resolved using template assemblies. I don't know this program but suspect it is performing a pairwise analysis for every piece of data in a genomics data set.

The solution is to either:

  1. find a bigger machine, e.g. a big multi-core machine and make sure the program distributes across every core.
  1. parallelise the calculation (an excellent way to overcome RAM problems), or,
  1. find an approximation to the calculation that is less computationally demanding, templates are a good way to circumvent this.