PlanWise Performance - Revision history

Peder at 11:59, 14 May 2018

2018-05-14T11:59:56Z

Peder at 11:23, 14 May 2018

2018-05-14T11:23:56Z

Peder: 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..."

2018-05-14T11:23:40Z

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..."

New page

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

← Older revision		Revision as of 11:59, 14 May 2018
Line 6:		Line 6:
	SQL Server version		SQL Server version
	PlanWise settings that control how many alternatives that are evaluated		PlanWise settings that control how many alternatives that are evaluated
		+
		+	==Hardware==
		+	====TPG time depends mainly on the processor====
		+
		+
		+	==SQL Server version==
		+	When using the report generator, SQL Select-queries are created and run on the SQL Server instance you have installed. There are large performance difference between the free SQL Server Express editions, and the Standard edition. SQL Server Standard allows for multiple CPU:s and 128GB of RAM usage, while Express is limited to one cpu and 1GB RAM. Express has a bulit-in database limit of 10GB database size, while Standard edition has no such limit. This may actually prevent you from using the Express edition for large problems. There are also differences between versions. In a test we made, execution times were decreased to 50-60% in version 2016 compared to version 2014.
		+
		+

← Older revision		Revision as of 11:23, 14 May 2018
Line 1:		Line 1:
		+	<!--
	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.		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.

Line 9:		Line 10:

	For large problems, computation times can be longer than		For large problems, computation times can be longer than
		+	-->