Locate other performance bottlenecks, document, and add testing constraints

[gwaybio]

Discussed in #195 (comment)

Add Memory/Time Testing Constraints for .merge_single_cells() (or others! 🙂 ) (Something like pytest-memray or similar): automate targeted performance tests to ensure operations within this project are usable by others as appropriate. Maybe this one spot was an outlier, but if there are other performance-heavy functions we could expand there as well.

[jenna-tomkinson]

@d33bs Is this issue resolved?

[d33bs]

@jenna-tomkinson - thanks, this is not yet resolved. In order for this to be resolved, I think the following steps would be needed (at a minimum):

• Capture expected "usual" time duration or memory amount for SingleCells.merge_single_cells to run.
• Add pytest-memray (or similar) dependency for dev / testing requirements.
• Add time duration or memory from above as a constraint for one or more SingleCells.merge_single_cells tests.
• Validate that the tests are able to pass for local development, within devcontainers associated with this project, and also Github actions (possibly finding a way to bind these in a reasonable manner)
• Document these new expectations where reasonable.