-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Panel rendering is pretty slow #416
Comments
We may be able to see some performance increases in general if we switch our Virtual DOM to Million.js (see #96) and switch our runtime to Bun (this would be a more massive undertaking). |
or perhaps just use plain JSX rather than a UI framework? |
Yeah, but, either way, I eventually wanted to switch out the Virtual DOM and runtime to Million.js and Bun for a long time. Million.js just wasn't stable back then although it is now. Bun is stable, but, it requires WSL for Windows since they're still working on a stable build for Windows (currently, unstable Windows build passes around 33% of Bun's internal tests). |
So kind of could help kill two birds with one stone (i don't remember if that's the saying lol). |
Expected Behavior
Rendering a single page should take ~16ms, but the panel page takes 20+ ms. This is quite bad when compared to the map page which has a render time of .5ms. (Performance should probably not be this bad when all we're displaying is a grid with some text)
Steps to Reproduce
.
Device Information
.
The text was updated successfully, but these errors were encountered: