Performance Test: Picod with a raspi3B+

[bsense-rius]

I've been testing the picod connected to a raspberry pi 3B+.

I've used the tick function in a loop (for write and read) with this scheme.
status, t1 = pico.tick()
pico.gpio_write(4, 1)
status, t2 = pico.tick()
res = picod.tick_diff(t1, t2)

I've seen that the write avg time is 15ms, and read avg time is 28ms (despite the 230400 bps of the serial port). I guess that is doubling because it requires sending the read request, and waiting the response.

It's fair but I wonder where the latency is generated. It is due to the raspberry pi 3B+? or is it in the picod? Is there any means to reduce it? An alternative could be to implement asyncio / awaitable read / write could avoid this "micro blocks".

Thank you for your attention

PS: I know we cannot compare it to pigpiod. I made similar tests with raspberry pi 3B+ with its GPIO and achieved outstanding values of 0.66ms for writes, 0,77ms for reads

[joan2937]

I rather lost interest in picod when the API broke and I could not rebuild the daemon. Currently I am concentrating on other activities.

Just about every API call has a reply parameter which can be set to one of the following values.

REPLY_NONE = 0
REPLY_NOW = 1
REPLY_LATER = 2

You could use REPLY_NONE for GPIO toggling (although in practice you'd probably use PWM).