From cda4fcb0fd3e9766a161cf3e5aa7c3283e7f7c9e Mon Sep 17 00:00:00 2001 From: Tim Hall Date: Thu, 19 May 2022 12:36:58 +0100 Subject: MLBEDSW-6563: networks failing with memory area exceeded in vela - For allocations that have a hard memory limit the Hill Climb allocator should be given more attempts to find a solution that would fit - The fix is to use a memory limit when there is a hard constraint, and a minimum iteration count, reset on every improvement, when there is a soft constraint - Added maximum number iterations CLI option Signed-off-by: Tim Hall Change-Id: I19ff53a0b68412de280263626778a3102cbe52fa --- ethosu/vela/scheduler.py | 1 + 1 file changed, 1 insertion(+) (limited to 'ethosu/vela/scheduler.py') diff --git a/ethosu/vela/scheduler.py b/ethosu/vela/scheduler.py index 0b79402a..1e311758 100644 --- a/ethosu/vela/scheduler.py +++ b/ethosu/vela/scheduler.py @@ -1312,6 +1312,7 @@ def _update_tensor_allocation(nng: Graph, arch: ArchitectureFeatures, options): tensor_allocator=options.tensor_allocator, verbose_allocation=options.verbose_allocation, cpu_tensor_alignment=options.cpu_tensor_alignment, + hillclimb_max_iterations=options.hillclimb_max_iterations, ) -- cgit v1.2.1