Watchdog Tripped Error on simulator for Edge 530/830

I am developing a datafield that performs complex computation.

It works fine for Edge 1030 both in the simulator and in a physical device.

However when I try to simulate for Edge 530/830 a Watchdog Tripped Error occurs. According to devices description in simulator.json files, watchdogcounter for them is as follows:

- Edge 1030: 2500000

- Edge 530/830: 160000

As a reference for comparison:

- Edge 1030plus: 2500000 (same as 1030)

- Edge 820: 160000 (same as 530/830)

I don´t really think this matches actual computation capacity 530/830 have, so I can manually modify watchdogcounter for 530/830 as workaround to be able to simulate.

Could I expect good behaviour for physical 530/830 devices? Will they perform at least as 1030 does?

jim_m_58 over 3 years ago

I'd trust the simulator here, and you many want to run something like Petr's Tree benchmark on the devices if you have them available as a way to gauge performance

https://apps.garmin.com/en-US/apps/ac3c85cc-e467-4610-9a3b-90f3b8fbecc8

Tripping the watchdog isn't really that common, and when I've seen it, it was due to a bug. But if there isn't a bug, you probably want to look at reworking your code. Avoiding doing something like calculating an average value in a large array but maintaining a running average instead.

InigoTolosa over 3 years ago in reply to jim_m_58

I have no physical device to check performance on 530/830.

And yes, I could optimize the code, but what I thought is that 530/830 hardware was able to performe better than 1030.

I didn´t expect so poor performance compared to 1030 as watchdogcounter shows (160000 / 2500000 --> 6%) and no improvement respect to 820.

jim_m_58 over 3 years ago in reply to InigoTolosa

I'd be surprised if the 530/830 performed better than the 1030, and the watchdog numbers indicate that's not the case.