pico-engine
pico-engine copied to clipboard
Picolab
When there are a large number of picos, the UX gets very sluggish
The picos page, for example, takes several seconds when there are more than a thousand picos.
The Rulesets tab takes many seconds to fully populate, as does the Testing tab.
Mostly, the pico engine seems to be sending the io.picolabs.pico-engine-ui/uiECI query many times. Perhaps there is a way to cache the answer, or delay making it until that ECI is actually needed.
The process which looks up and displays the names of the child picos is extremely sluggish. A lot seems to be happening in the browser, but the pico engine is also being heavily used. After several minutes the node process calmed down, but the UI is only showing the names of the first six child picos (out of 5000+).