MerginMaps / MerginMaps/geodiff
Improve memory usage of `concat_changes` method
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 183
- Forks
- 21
- Avg merge
- 9d 11h
- Merged PRs (30d)
- 2
Description
Problem
When using the geodiff concat_changes method with a large diff file (e.g., 350 MB), the RAM usage increases unexpectedly to approximately 3 GB. This memory peak can lead to Out of Memory (OOM) errors in server deployments where container resources are limited.
@wonder-sk I sent you the problematic diff file in private channel.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the geodiff concat_changes method and reproduce the report with a large diff file around 350 MB. Investigate the unexpected RAM peak and verify that the method completes without causing excessive memory growth or out-of-memory failures in constrained server deployments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100