sharpbrick/powered-up

Re-implement DiscoverPorts based on a request/response architecture

tthiery opened this issue · 1 comments

Currently the DiscoverPorts works in an event style programming matters. It fires many port discovery requests and awaits their responses. While this might have some performance benefits, with fast adapters it might overload the hub.

A better architecture is a request / response pair.

See conversation around #145

  • Pre Refactoring Test Run (Technic Medium Hub + 2 XL Motors): 30s
  • Post Refactoring Test Run: 33s => acceptable
  • Output Identical