Skip to content
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

chore: update gtx to 0.0.57 #1743

Merged
merged 1 commit into from
Sep 24, 2024
Merged

chore: update gtx to 0.0.57 #1743

merged 1 commit into from
Sep 24, 2024

Conversation

lifeart
Copy link
Contributor

@lifeart lifeart commented Sep 14, 2024

image image

Bumping gxt from v37 to v57, memory usage & cleanup logic should be improved.
Also, see some regression in create-many case.

Prev: #1593

@lifeart lifeart changed the title chore: update gtx to 0.0.55 chore: update gtx to 0.0.56 Sep 15, 2024
update gtx to 0.0.55

update gtx to 0.0.56
@lifeart lifeart changed the title chore: update gtx to 0.0.56 chore: update gtx to 0.0.57 Sep 16, 2024
@krausest krausest merged commit 332f83c into krausest:master Sep 24, 2024
@krausest
Copy link
Owner

Here's a screenshot from an incremental run (left new version, right old version).
Please note that vanillajs was slower on the left. I'm a bit disappointed with that because I'm trying to solve #1721, but as you can see vanillajs perfomed was 0.2 slower (even after reboot and on AC). So I think it's plausible to assume that performance for all updated versions would be better in a full run, especially for gxt which was even a bit faster in the incremental run.
Screenshot 2024-09-25 at 08 05 07

@lifeart lifeart deleted the update-gxt-5 branch September 25, 2024 06:24
@lifeart
Copy link
Contributor Author

lifeart commented Sep 25, 2024

@krausest thank you for merge, run and additional details!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants