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
Hydrus version:428
Platform: Mac 10.13 (source)
OS specifics:
What happens
When commiting a very large archive/delete it seems to take forever, I suspect it takes no more time than usual but the time for an individual update is so long that hydrus just seems to hang for like 1 or 2 hours. I'm not sure why this is, it should only take µseconds to update a table entry.
Steps to reproduce
Archive/delete 1000 items before commit. Maybe perform some big searches first.
Desired outcome
An archive delete especially on a bulk selection should not take very long.
It appears that mid bulk archive delete update that counts in tabs update, I expect this means that his means hydrus is trying to update the GUI for every single item as it is deleted. (This is also a problem with just normal selection deleted) When performing an action on a selection of items, the pubsub step should occur after the entire selection has been processed, not for each item, as this will retrieve state which will very soon be wrong again anyway, and is very expensive.
The text was updated successfully, but these errors were encountered:
Thank you for this report. I apologise for the late response. I know this is still a problem for some, so I have broke the final commit after an archive/delete into batches of 64 files, with pauses in between if the UI is currently busy. Please let me know if you still have trouble here!
Environment
Hydrus version:428
Platform: Mac 10.13 (source)
OS specifics:
What happens
When commiting a very large archive/delete it seems to take forever, I suspect it takes no more time than usual but the time for an individual update is so long that hydrus just seems to hang for like 1 or 2 hours. I'm not sure why this is, it should only take µseconds to update a table entry.
Steps to reproduce
Desired outcome
An archive delete especially on a bulk selection should not take very long.
It appears that mid bulk archive delete update that counts in tabs update, I expect this means that his means hydrus is trying to update the GUI for every single item as it is deleted. (This is also a problem with just normal selection deleted) When performing an action on a selection of items, the pubsub step should occur after the entire selection has been processed, not for each item, as this will retrieve state which will very soon be wrong again anyway, and is very expensive.
The text was updated successfully, but these errors were encountered: