Opened 22 months ago

Last modified 20 months ago

#855 new optimization

Calculating many trees by macro uses too many resources

Reported by: westram Owned by: devel
Priority: normal Milestone:
Component: ARB_NTREE Version: SVN
Keywords: tree gde external Cc:

Description

Scenario:

  • calculate e.g. 50 trees using fasttree triggered by a arb macro

Effects:

  • all tree calculations start simultaneously
    • memory usage maximized
    • CPU workload maximized
  • sequence data is exported for each tree calculation
    • this data is stored uncompressed and aligned ⇒ it may easily use Gbs of diskspace for each tree
    • that data is not deleted when tree calculation finishes
  • tree calculation does not run import + cleanup w/o user interaction
  • produced trees all have random names

Wanted improvements:

  • allow to limit the maximum number of external tools running simultaneously
  • cleanup input data when (tree) calculation finishes
  • allow to import trees w/o user interaction
  • allow to define resulting names via macro (#461)

related: #594, #595, #343

Change History (1)

comment:1 Changed 20 months ago by westram

  • Priority changed from major to normal

[cost-benefit analysis resulted in negative value]

Note: See TracTickets for help on using tickets.