PlanWise Performance

From Heureka Wiki
Revision as of 13:23, 14 May 2018 by Peder (talk | contribs) (Created page with "In this article we discuss things you can do to minimize computation times in PlanWise. For very large problems (say at least 25000 treatment units) it may take hours, or even...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

In this article we discuss things you can do to minimize computation times in PlanWise. For very large problems (say at least 25000 treatment units) it may take hours, or even days, to generate alternatives with the treatment program generator (TPG). These alternatives are used as input to the optimzation model. The optimization model involves a so called build step, in which a user-defined modul is interpreted, compiled, populated with data, and transformed to a format that a solver can read. This step can also be very time consuming, while the time for solving the problem can be suprisingly short, depending on the complexity of the model and whether it is an LP or MIP problem. However, this is a general optimization problem issue, not specific for PlanWise. When solved as ordinary LP-problem, solution times is usually very short when using a commercial solver such as Gurobi or Cplex.

There are four areas you can look at to minimize computation times: Hardware SQL Server version PlanWise settings that control how many alternatives that are evaluated


For large problems, computation times can be longer than