Raiden is slow on slow hardware

[eorituz]

Abstract

Raiden tx from a raspberry pi zero to an udoo x86 takes extremly long.
If the Udoo runs 6 Raiden nodes and the Pi zero 1 it takes 45-75s to complete a Tx (almost independent of the number of hops.

Plot

I tested a transaction from the pi zero (pi@raspberrypi) to the udoo (train@demo) with only one raiden node running on each machine (it was ofc a direct transfer). It took ~40s to complete the transfer. Checkout the video to see what I did in particular.

Specification

Used Raiden version 0.18.1
Raspian on the RPi
Ubuntu 18.04 on the Udoo

Logs

(Tx started at ~13:51 GMT)
raspberry_sender.log
udoo_receiver.log

Video

A short video of what I did, including memory usage of Pi
https://drive.google.com/file/d/1K1l0oIx8IGBM0Tp45IFCkKj-lLIBEg_B/view?usp=sharing

[eorituz]

Benchmarks for Raspberry Pi Model 3 B+

Direct transfers from a Raspberry Pi Model 3 B+ is a lot faster.
Using a class 10 Intenso 90Mbps SD Card the transaction time is steadily between 5 and 5.5s per transaction.
Writing the datadir in /dev/shm (using the flag --datadir /dev/shm ) reduce the transaction time about 10% to ~4.5s/transaction

Specification

Used Raiden version 0.18.1
Raspian on the RPi

[hackaugusto]

Related: #61

[eorituz]

Ulo and I suspect, that the long transaction time is caused by the EC recover function, which needs to be done for every received message.

[palango]

Ulo and I suspect, that the long transaction time is caused by the EC recover function, which needs to be done for every received message.

Is there something we can do in that case? The crypto-code should already be native code. @ulope

[karlb]

I assume the performance on the pi is much better today. @ezdac since you do some testing on this, please reopen if this is not the case.