-
Notifications
You must be signed in to change notification settings - Fork 132
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
Hacky/quick generation of fake data for perf testing (requries db resets) #647
Conversation
Is this going to work? |
Yeah it works -- I used this for #642. I don't plan to merge this, it's pretty hacky (and requires a db reset) lol, just wanted to check the diff. |
Hey, do you know why trimming one table, takes a long time to do it. I think my wsl ubuntu is fcked... |
Not related to this PR or bpy, please ask on the Discord instead or google. |
|
that's even slower than truncating because of the way it deallocates + it writes to the undo log |
If you do it in a transaction then not really lol |
I don't think transactions have anything to do with this. On DELETE, every row is locked separately, while TRUNCATE locks the whole table. |
truncate tries to delete the data but sometimes gives an error to fix it |
Describe your changes
Related Issues / Projects
Checklist