Troubleshooting calculation performance - Revision history

Maxim@tygron.com: /* When do long calculation times appear */

2026-07-09T07:35:10Z

When do long calculation times appear

← Older revision		Revision as of 07:35, 9 July 2026
Line 12:		Line 12:
	* When uploading excel sheets		* When uploading excel sheets

	''These are discrete processing events.''		''*These are discrete processing events.''

	==Probable causes of long calculation times==		==Probable causes of long calculation times==

Maxim@tygron.com at 07:34, 9 July 2026

2026-07-09T07:34:53Z

← Older revision		Revision as of 07:34, 9 July 2026
Line 12:		Line 12:
	* When uploading excel sheets		* When uploading excel sheets

	''*These are ~~single moments of~~ processing~~, and should not be considered too harshly~~.''		''These are discrete processing events.''

	==Probable causes of long calculation times==		==Probable causes of long calculation times==

Frank@tygron.nl at 11:42, 8 July 2026

2026-07-08T11:42:58Z

Maxim@tygron.com at 15:40, 9 June 2026

2026-06-09T15:40:16Z

← Older revision		Revision as of 15:40, 9 June 2026
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 [[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.		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 map]]. 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: /* 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===

← Older revision		Revision as of 11:42, 8 July 2026
Line 24:		Line 24:

	=====Many areas (or polygons)=====		=====Many areas (or polygons)=====
	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. The {{software}} first performs a quick check; if a polygon is affected, it then executes a thorough calculation of the 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.

	Buildings 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.
Line 41:		Line 41:

	===Excel sheets===		===Excel sheets===
	~~The~~ {{software}}~~'s calculations are~~ optimized ~~greatly~~, ~~but with the ability to add your own excel~~ sheets ~~it's possible to add~~ more complex ~~calculations to the {{software}}'s~~ tasks. If these calculations are not optimized as well, the {{software}} will spend more time to perform these calculations. When designing your own calculation sheets, there are a number precautions you can take to prevent the {{software}} slowing down too much on them. This can seem tricky, because when opened in Excel a sheet may seem to calculate quite quickly. However, when a different application, such as the {{software}}, handles an excel sheet, the calculations will take a bit longer. Under some circumstances, these small increases in calculation time can add up.		While the {{software}} is highly optimized, adding custom Excel sheets can introduce more complex calculation tasks. If these calculations are not optimized as well, the {{software}} will spend more time to perform these calculations. When designing your own calculation sheets, there are a number precautions you can take to prevent the {{software}} slowing down too much on them. This can seem tricky, because when opened in Excel a sheet may seem to calculate quite quickly. However, when a different application, such as the {{software}}, handles an excel sheet, the calculations will take a bit longer. Under some circumstances, these small increases in calculation time can add up.

	For debugging purposes, the {{software}} displays the calculation time for excel indicators when they are selected in the editor.		For debugging purposes, the {{software}} displays the calculation time for excel indicators when they are selected in the editor.

	=====Complex excel formulas=====		=====Complex excel formulas=====
	Excel is a powerful tool because of the functions and formulas it provides. However, some of the functions excel provides are more complex than others. For example, ~~functions such as~~ MATCH, which ~~look up an value in~~ a ~~list by comparing it to another value, are~~ more ~~complex~~ than INDEX, which ~~simply~~ returns ~~the~~ value ~~in a given place in a list~~. It's not an issue to use a computationally heavy function here and there, but where possible they should be used as little as possible. Functions like IF and SUMIF should be avoided as well where possible, though they are not as problematic.		Excel is a powerful tool because of the functions and formulas it provides. However, some of the functions excel provides are more complex than others. For example, MATCH (which compares values to find a match) is more computationally expensive than INDEX (which returns a specific position's value). It's not an issue to use a computationally heavy function here and there, but where possible they should be used as little as possible. Functions like IF and SUMIF should be avoided as well where possible, though they are not as problematic.

	One concrete example is that often MATCH and INDEX are used together to look up a value and return something on the same row or column. If multiple values are to be retrieved from that same row, rather than using MATCH multiple times to determine the row number, use it once and store the row number in a separate cell. Then every time you need to retrieve values from that row, refer to that cell.		One concrete example is that often MATCH and INDEX are used together to look up a value and return something on the same row or column. If multiple values are to be retrieved from that same row, rather than using MATCH multiple times to determine the row number, use it once and store the row number in a separate cell. Then every time you need to retrieve values from that row, refer to that cell.
Line 69:		Line 69:

	=====Heavy calculations=====		=====Heavy calculations=====
	Some calculation models, such as the flooding overlay, have an inherently more complicated calculation. ~~Especially~~ iterative processes, ~~in which~~ calculations are repeated ~~a large number of~~ times. In combination with an accurate grid size, these calculations can take a long time to complete. The more data the calculation relies on, the longer the system will be occupied preparing the data for the calculation. ~~The more~~ interactions ~~each grid cell has to calculate,~~ and ~~the more~~ iterations ~~need~~ to ~~be calculated, the more~~ calculations ~~will need to be made in total~~. And the more output the overlay is set to create, the longer it will take to transfer all new data back to the end-user.		Some calculation models, such as the flooding overlay, have an inherently more complicated calculation. This is especially true for iterative processes, where calculations are repeated many times. In combination with an accurate grid size, these calculations can take a long time to complete. The more data the calculation relies on, the longer the system will be occupied preparing the data for the calculation. Increased cell interactions and iterations lead to a higher total number of calculations. And the more output the overlay is set to create, the longer it will take to transfer all new data back to the end-user.

	Note that these overlays may have more calculation- and implementation- specific settings which balance speed and accuracy. Tweaking these settings will affect the outcome of the calculations, but represent a trade-off between responsiveness and detail.		Note that these overlays may have more calculation- and implementation- specific settings which balance speed and accuracy. Tweaking these settings will affect the outcome of the calculations, but represent a trade-off between responsiveness and detail.