Originally created by @terenzeyuen on GitHub (Dec 16, 2016).
We noticed whenever we trigger commit with large imports (30k record), UI thread stalls for a few seconds. Is this normal? @JohnEstropia
Originally created by @terenzeyuen on GitHub (Dec 16, 2016).
We noticed whenever we trigger commit with large imports (30k record), UI thread stalls for a few seconds. Is this normal? @JohnEstropia
adam
added the question label 2025-12-29 15:24:49 +01:00
Do you use ListMonitors? Saving objects will trigger updates on monitors, which notifies the UI on the main thread. So if you save a lot of objects at once those will have noticeable effects on the UI.
My suggestion is to save your 30k records into chunks. Say, one beginAsynchronous for each 1000 items.
@JohnEstropia commented on GitHub (Dec 16, 2016):
Do you use ListMonitors? Saving objects will trigger updates on monitors, which notifies the UI on the main thread. So if you save a lot of objects at once those will have noticeable effects on the UI.
My suggestion is to save your 30k records into chunks. Say, one `beginAsynchronous` for each 1000 items.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @terenzeyuen on GitHub (Dec 16, 2016).
We noticed whenever we trigger commit with large imports (30k record), UI thread stalls for a few seconds. Is this normal? @JohnEstropia
@JohnEstropia commented on GitHub (Dec 16, 2016):
Do you use ListMonitors? Saving objects will trigger updates on monitors, which notifies the UI on the main thread. So if you save a lot of objects at once those will have noticeable effects on the UI.
My suggestion is to save your 30k records into chunks. Say, one
beginAsynchronousfor each 1000 items.@terenzeyuen commented on GitHub (Dec 29, 2016):
Thanks !