You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, every app that uses Layout has to include its own copy. Parsing it in initially takes 25ms by itself, and then executing it to render on something like a navigation message takes 240ms when running from internal flash would be 220ms.
... so if we built it into the Bangle.js firmware we'd save around 45ms loading something like a navigation message.
The reason we didn't build it in initially was that it was changing rapidly, but the last real change was made a year ago so I think we'd be safe.
Of course if it were to need changes after this, realistically we're looking at waiting until the next Bangle.js firmware release before those changes could go it...
Any thoughts?
The text was updated successfully, but these errors were encountered:
Just to add to this, we also have some "ram" keywords to aid performance from external flash. When running on internal flash those could be removed and would likely get it running even faster.
Right now, every app that uses Layout has to include its own copy. Parsing it in initially takes 25ms by itself, and then executing it to render on something like a navigation message takes 240ms when running from internal flash would be 220ms.
... so if we built it into the Bangle.js firmware we'd save around 45ms loading something like a navigation message.
The reason we didn't build it in initially was that it was changing rapidly, but the last real change was made a year ago so I think we'd be safe.
Of course if it were to need changes after this, realistically we're looking at waiting until the next Bangle.js firmware release before those changes could go it...
Any thoughts?
The text was updated successfully, but these errors were encountered: