use with_entities to pull only cond and counterbalance #563
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Seems like a reasonable improvement (particularly because all that potentially heavy task data gets stored in that one Too bad there is no-one managing this project anymore to accept the pull-request. |
I added you to the repo in a way that should allow merging PRs |
jacob-lee
approved these changes
Jul 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
surprised no one has run into this issue before - my task app was using ridiculous amounts of memory from querying participants just to assign cond/counterbalance
I guess others probably save smaller/simpler/more efficiently coded datastrings or collect data from fewer participants for each codeversion
using .with_entities to just grab the cond and counterbalance columns seems more efficient