The perfect storm of Firebase Store + Elms missing language semantics of monads/signals + architecture causes the webshop to have some performance issues as of now. There are a couple of reasons for this, which I try to cover here. There are some improvements we can do short term but should look into how to scale this better as the webshop grows to have more non-trivial requirements.
This is not a complete list, nor is it well defined/described. Just brain-dumping my initial thoughts before they escape forever.
Initial issues identified
Multiple tick subscriptions (to update time) causes several updates per second. Should only have one globally?
No heuristics on state updates and data changes. So the entire state tree updates on every tick even though a specific page is not active. This means that even pages that users never use, steals memory and CPU cycles unnecessarily.
Due to Firebase Store not having windowing/paging we have to load everything into memory. There are some logic to try to optimize CPU use (at the cost of memory), but it's still some work being done reactively which will cause performance to be gradually worse as the number of reservations and fare contracts in Firebase Store increase.
Nature of POSIX current time state ticks and the use of The Elm Arcitecture™ causes data not to be able to be memoized/lazy checked. For instance, doing Html.lazy with reference checks on input would never work as time increases. To optimize this we'd have to move the ticks outside and reduce the resolution on ticks.
Example output
Simple performance audit when not interaction. Show problem with CPU usage on idle.
The perfect storm of Firebase Store + Elms missing language semantics of monads/signals + architecture causes the webshop to have some performance issues as of now. There are a couple of reasons for this, which I try to cover here. There are some improvements we can do short term but should look into how to scale this better as the webshop grows to have more non-trivial requirements.
This is not a complete list, nor is it well defined/described. Just brain-dumping my initial thoughts before they escape forever.
Initial issues identified
Example output
Simple performance audit when not interaction. Show problem with CPU usage on idle.