Troubleshooting calculation performance - Revision history

Maxim@tygron.com: /* Multiple results */

2026-04-13T12:24:29Z

Multiple results

← Older revision		Revision as of 12:24, 13 April 2026
Line 76:		Line 76:

	=====Multiple results=====		=====Multiple results=====
	Some overlays, such as ~~the [[Subsidence (Overlay)\|subsidence overlay]] or~~ the [[Flooding (Overlay)\|flooding overlay]], perform calculations which may generate a variety of relevant results. For each instance of such an overlay, a complete calculation must be performed to get the results for each. This is because the settings for each overlay can differ. Even if the only differing aspect is the result or output type, they are still considered separate calculations. Overlays with multiple result types offer a configuration where multiple result types can be added to such an overlay as child overlays. These are not entirely separate overlays, but separate output layers for the same calculation.		Some overlays, such as the [[Flooding (Overlay)\|flooding overlay]], perform calculations which may generate a variety of relevant results. For each instance of such an overlay, a complete calculation must be performed to get the results for each. This is because the settings for each overlay can differ. Even if the only differing aspect is the result or output type, they are still considered separate calculations. Overlays with multiple result types offer a configuration where multiple result types can be added to such an overlay as child overlays. These are not entirely separate overlays, but separate output layers for the same calculation.

	Where possible, avoid creating separate calculating overlays with (virtually) unchanged parameters. Where possible, use the child result types to provide multiple types of output, and take care to make sure that they are child results of a single main calculation.		Where possible, avoid creating separate calculating overlays with (virtually) unchanged parameters. Where possible, use the child result types to provide multiple types of output, and take care to make sure that they are child results of a single main calculation.

Maxim@tygron.com at 12:24, 13 April 2026

2026-04-13T12:24:03Z

← Older revision		Revision as of 12:24, 13 April 2026
Line 64:		Line 64:

	=====Grid overlays=====		=====Grid overlays=====
	A few [[Overlay]]s in the {{software}} are actually [[Grid overlay\|calculation models]]. These include, among others, the overlays for [[Livability (Overlay)\|livability]], [[Subsidence (Overlay)\|subsidence]], [[Heat Stress Overlay\|heat]], and [[Traffic Noise (Overlay)\|traffic noise]]. These calculations happen in the form of a grid; parts of which are updated whenever their underlying data is changed. The size of the cells of those grids can be changed. The smaller the cells, the more accurate the calculations and the shapes generated by the overlay. However, smaller cells mean more calculations. Selecting a smaller cell size means the {{software}} will spend a greater amount of time to recalculate (parts of) an overlay.		A few [[Overlay]]s in the {{software}} are actually [[Grid overlay\|calculation models]]. These include, among others, the overlays for [[Livability (Overlay)\|livability]], [[Subsidence (Overlay)\|subsidence]], [[Heat Stress Overlay\|heat stress]], and [[Traffic Noise (Overlay)\|traffic noise]]. These calculations happen in the form of a grid; parts of which are updated whenever their underlying data is changed. The size of the cells of those grids can be changed. The smaller the cells, the more accurate the calculations and the shapes generated by the overlay. However, smaller cells mean more calculations. Selecting a smaller cell size means the {{software}} will spend a greater amount of time to recalculate (parts of) an overlay.

	Where possible, set the grid size of calculated as low as is required for your use-case but no lower.		Where possible, set the grid size of calculated as low as is required for your use-case but no lower.

Maxim@tygron.com at 12:23, 13 April 2026

2026-04-13T12:23:50Z

← Older revision		Revision as of 12:23, 13 April 2026
Line 64:		Line 64:

	=====Grid overlays=====		=====Grid overlays=====
	A few [[Overlay]]s in the {{software}} are actually [[Grid overlay\|calculation models]]. These include, among others, the overlays for [[Livability (Overlay)\|livability]], [[Subsidence (Overlay)\|subsidence]], [[Heat (Overlay)\|heat]], and [[Traffic Noise (Overlay)\|traffic noise]]. These calculations happen in the form of a grid; parts of which are updated whenever their underlying data is changed. The size of the cells of those grids can be changed. The smaller the cells, the more accurate the calculations and the shapes generated by the overlay. However, smaller cells mean more calculations. Selecting a smaller cell size means the {{software}} will spend a greater amount of time to recalculate (parts of) an overlay.		A few [[Overlay]]s in the {{software}} are actually [[Grid overlay\|calculation models]]. These include, among others, the overlays for [[Livability (Overlay)\|livability]], [[Subsidence (Overlay)\|subsidence]], [[Heat Stress Overlay\|heat]], and [[Traffic Noise (Overlay)\|traffic noise]]. These calculations happen in the form of a grid; parts of which are updated whenever their underlying data is changed. The size of the cells of those grids can be changed. The smaller the cells, the more accurate the calculations and the shapes generated by the overlay. However, smaller cells mean more calculations. Selecting a smaller cell size means the {{software}} will spend a greater amount of time to recalculate (parts of) an overlay.

	Where possible, set the grid size of calculated as low as is required for your use-case but no lower.		Where possible, set the grid size of calculated as low as is required for your use-case but no lower.

Frank@tygron.nl: /* Grid overlays */

2026-03-05T13:49:54Z

Grid overlays

← Older revision		Revision as of 13:49, 5 March 2026
Line 64:		Line 64:

	=====Grid overlays=====		=====Grid overlays=====
	A few [[Overlay]]s in the {{software}} are actually [[Grid overlay\|calculation models]]. These include, among others, the overlays for [[Livability (Overlay)\|livability]], [[Subsidence (Overlay)\|subsidence]], [[Heat (Overlay)\|heat]], and [[Traffic ~~noise~~ (Overlay)\|traffic noise]]. These calculations happen in the form of a grid; parts of which are updated whenever their underlying data is changed. The size of the cells of those grids can be changed. The smaller the cells, the more accurate the calculations and the shapes generated by the overlay. However, smaller cells mean more calculations. Selecting a smaller cell size means the {{software}} will spend a greater amount of time to recalculate (parts of) an overlay.		A few [[Overlay]]s in the {{software}} are actually [[Grid overlay\|calculation models]]. These include, among others, the overlays for [[Livability (Overlay)\|livability]], [[Subsidence (Overlay)\|subsidence]], [[Heat (Overlay)\|heat]], and [[Traffic Noise (Overlay)\|traffic noise]]. These calculations happen in the form of a grid; parts of which are updated whenever their underlying data is changed. The size of the cells of those grids can be changed. The smaller the cells, the more accurate the calculations and the shapes generated by the overlay. However, smaller cells mean more calculations. Selecting a smaller cell size means the {{software}} will spend a greater amount of time to recalculate (parts of) an overlay.

	Where possible, set the grid size of calculated as low as is required for your use-case but no lower.		Where possible, set the grid size of calculated as low as is required for your use-case but no lower.

Frank@tygron.nl: /* When do long calculation times appear */

2026-03-05T13:49:28Z

When do long calculation times appear

← Older revision		Revision as of 13:49, 5 March 2026
Line 5:		Line 5:
	* When performing an [[action]]		* When performing an [[action]]
	* When firing an [[event]]		* When firing an [[event]]
	* When switching [[~~levels~~]]		* When switching [[scenario]]

	* When loading a project into the [[editor]]*		* When loading a project into the [[editor]]*

Rudolf@tygron.nl: /* Complex areas (or polygons) */

2026-02-25T12:04:25Z

Complex areas (or polygons)

← Older revision		Revision as of 12:04, 25 February 2026
Line 39:		Line 39:

	Where possible, keep polygons as simple as possible. There is no easy measure for determining the complexity of a polygon. If you find a polygon which is long, thin, has many corners, branches or holes, try to get the polygon smoothed out, or cut up into smaller polygons with fewer corners and subpolygons.		Where possible, keep polygons as simple as possible. There is no easy measure for determining the complexity of a polygon. If you find a polygon which is long, thin, has many corners, branches or holes, try to get the polygon smoothed out, or cut up into smaller polygons with fewer corners and subpolygons.

	~~[[File:YoutubeLogo1.jpg\|link=https://youtu.be/viDLDDj29oY/\|thumb\|left\|Hoe kan het dat mijn project traag is geworden na het inlezen van geodata? (Dutch only)]]{{clear}}~~

	===Excel sheets===		===Excel sheets===

Frank@tygron.nl at 10:34, 1 March 2023

2023-03-01T10:34:52Z

← Older revision		Revision as of 10:34, 1 March 2023
Line 21:		Line 21:
	[[File:YoutubeLogo1.jpg \| link=https://youtu.be/jZIArca3l8A/\|thumb\|left\|Performance Overview Panel (Dutch only)]]{{clear}}		[[File:YoutubeLogo1.jpg \| link=https://youtu.be/jZIArca3l8A/\|thumb\|left\|Performance Overview Panel (Dutch only)]]{{clear}}
	===Areas (And polygons)===		===Areas (And polygons)===
	Because many calculations in the {{software}} rely on spatial data, many things in the {{software}} have some form of polygon: a shape which, in one way or another, is "in" the [[~~3D environment~~]]. Buildings, zones and areas are most easily recognized as polygons. But other things such as land [[ownership]] and [[terrain\|land types]] do too. When data changes, the {{software}} may have to see whether this has affected any polygons. If it has, it means things like the surface area of something has changed, or that some element now is or isn't overlapping with another polygon anymore. The {{software}} tries to find ways to avoid these calculations as much as possible, but they must occur at some point. The following situations may cause the {{software}} to calculate too much when it comes to polygons.		Because many calculations in the {{software}} rely on spatial data, many things in the {{software}} have some form of polygon: a shape which, in one way or another, is "in" the [[project area]]. Buildings, zones and areas are most easily recognized as polygons. But other things such as land [[ownership]] and [[terrain\|land types]] do too. When data changes, the {{software}} may have to see whether this has affected any polygons. If it has, it means things like the surface area of something has changed, or that some element now is or isn't overlapping with another polygon anymore. The {{software}} tries to find ways to avoid these calculations as much as possible, but they must occur at some point. The following situations may cause the {{software}} to calculate too much when it comes to polygons.

	=====Many areas (or polygons)=====		=====Many areas (or polygons)=====

Frank@tygron.nl at 15:30, 23 February 2023

2023-02-23T15:30:16Z

← Older revision		Revision as of 15:30, 23 February 2023
Line 8:		Line 8:

	* When loading a project into the [[editor]]*		* When loading a project into the [[editor]]*
	* When starting or stopping a [[Test Run~~\|test run~~]]*		* When starting or stopping a [[Test Run]]*
	* When adding/removing/changing anything spatial ([[zones]], [[buildings]], [[areas]], etc)		* When adding/removing/changing anything spatial ([[zones]], [[buildings]], [[areas]], etc)
	* When uploading excel sheets		* When uploading excel sheets
Line 55:		Line 55:

	======Calltree recording======		======Calltree recording======
	To help debugging excel files to find significant calculation times, you can use the [[Calltree recording]] function. During a [[~~testrun~~]] in the [[editor]], this option will cause the {{software}} to track how long it takes to calculate each cell in the sheet.		To help debugging excel files to find significant calculation times, you can use the [[Calltree recording]] function. During a [[Test Run]] in the [[editor]], this option will cause the {{software}} to track how long it takes to calculate each cell in the sheet.

	=====X-queries=====		=====X-queries=====

Frank@tygron.nl: /* Areas (And polygons) */

2022-10-27T15:09:14Z

Areas (And polygons)

← Older revision		Revision as of 15:09, 27 October 2022
Line 21:		Line 21:
	[[File:YoutubeLogo1.jpg \| link=https://youtu.be/jZIArca3l8A/\|thumb\|left\|Performance Overview Panel (Dutch only)]]{{clear}}		[[File:YoutubeLogo1.jpg \| link=https://youtu.be/jZIArca3l8A/\|thumb\|left\|Performance Overview Panel (Dutch only)]]{{clear}}
	===Areas (And polygons)===		===Areas (And polygons)===
	Because many calculations in the {{software}} rely on spatial data, many things in the {{software}} have some form of polygon: a shape which, in one way or another, is "in" the [[3D environment]]. ~~Constructions~~, zones and areas are most easily recognized as polygons. But other things such as land [[ownership]] and [[terrain\|land types]] do too. When data changes, the {{software}} may have to see whether this has affected any polygons. If it has, it means things like the surface area of something has changed, or that some element now is or isn't overlapping with another polygon anymore. The {{software}} tries to find ways to avoid these calculations as much as possible, but they must occur at some point. The following situations may cause the {{software}} to calculate too much when it comes to polygons.		Because many calculations in the {{software}} rely on spatial data, many things in the {{software}} have some form of polygon: a shape which, in one way or another, is "in" the [[3D environment]]. Buildings, zones and areas are most easily recognized as polygons. But other things such as land [[ownership]] and [[terrain\|land types]] do too. When data changes, the {{software}} may have to see whether this has affected any polygons. If it has, it means things like the surface area of something has changed, or that some element now is or isn't overlapping with another polygon anymore. The {{software}} tries to find ways to avoid these calculations as much as possible, but they must occur at some point. The following situations may cause the {{software}} to calculate too much when it comes to polygons.

	=====Many areas (or polygons)=====		=====Many areas (or polygons)=====

Maxim@tygron.com at 15:52, 7 October 2022

2022-10-07T15:52:44Z

← Older revision		Revision as of 15:52, 7 October 2022
Line 9:		Line 9:
	* When loading a project into the [[editor]]*		* When loading a project into the [[editor]]*
	* When starting or stopping a [[Test Run\|test run]]*		* When starting or stopping a [[Test Run\|test run]]*
	* When adding/removing/changing anything spatial ([[zones]], [[~~constructions~~]], [[areas]], etc)		* When adding/removing/changing anything spatial ([[zones]], [[buildings]], [[areas]], etc)
	* When uploading excel sheets		* When uploading excel sheets

Line 26:		Line 26:
	The more polygons exist, the more the {{software}} will have to check to see whether they require an update. A (quick) calculation will be performed to see if the change has affected a given polygon, and if it has, a more thorough calculation will be performed to calculate the actual resulting data. If there are more polygons, more will need to be checked that first time, to see whether they are affected by a given change.		The more polygons exist, the more the {{software}} will have to check to see whether they require an update. A (quick) calculation will be performed to see if the change has affected a given polygon, and if it has, a more thorough calculation will be performed to calculate the actual resulting data. If there are more polygons, more will need to be checked that first time, to see whether they are affected by a given change.

	~~Constructions~~ form an exception. They are used less as "containers" for calculations, so aren't checked in the same manner as often.		Buildings form an exception. They are used less as "containers" for calculations, so aren't checked in the same manner as often.

	Where possible, use fewer polygons rather than more. Also, be sure to clean up polygons you no longer use (for example: unused areas). With the exception of ~~constructions~~, the amount of polygon elements (areas, zones, etc) in a project should not be more than a thousand.		Where possible, use fewer polygons rather than more. Also, be sure to clean up polygons you no longer use (for example: unused areas). With the exception of buildings, the amount of polygon elements (areas, zones, etc) in a project should not be more than a thousand.

	=====Large areas (or polygons)=====		=====Large areas (or polygons)=====