-
Notifications
You must be signed in to change notification settings - Fork 326
Client side journal rendering #2080
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
Conversation
09a9f01 to
b65127e
Compare
f116376 to
f8d30a2
Compare
e0b11c1 to
c89f9b6
Compare
9354a2c to
c3da200
Compare
bac0bb4 to
2df3825
Compare
0acaf0c to
151a21e
Compare
|
This seems stale and quite far from being ready - I'll close the PR. The journal is now fetched in pages and should thus render quicker already. Rendering it in the frontend might still be an improvement (if also using some sort of virtual list), so if you want to continue on this topic, feel free to open another PR |
|
I got sidetracked doing other things 😅. I mainly make this since I wanted to see the journal when I'm on mobile. |
Move journal rendering to client side, making use of virtual list component.
It's able to render huge journal with 100k transactions (generated by this script) with ease, now the bottleneck is the request to the server. One solution is to use orjson instead of simplejson, which cuts it from 8 seconds to 4 seconds. Reverted the change since it breaks tests.
Close #1410
Close #1814