I am working on an app which loads many resources when it first starts up. Elm handles this wonderfully, except that that the frame rate goes down. This seems to be because the elm runtime processes every message between each animation frame since no individual message takes long enough to process that a frame would be skipped.
I’ve made an example of what I’m talking about on Ellie. The app displays the frame delta in milliseconds and spawns a bunch of messges each frame. When
incrementsPerFrame is small, the page hums along at 60fps. When it is
10000, it runs at 7fps on my computer.
I would expect that the runtime would only process as many messages as it had time for each frame, keeping the unprocessed messages at the front of the queue for the next frame.
I would first like to point this out as a problem with an actual app that I have written and second to ask if anyone has any workarounds for this that have worked for them.
I think this is what I was looking for: Asynchronous parsing