Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

re-evaluate garbage collection considering its bandwidth costs

Open
#381 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
distributed-systems, performance

Research direction

No files or tests are named. Start by locating the distarray garbage-collection path and the per-engine roundtrip, then determine how bandwidth costs should be weighed against memory savings. Done requires an agreed behavior for when collection occurs and validation of that behavior.

Written by the indexing model from the issue text.

Description

enhancement

Currently when a distarray is garbage collected, it costs one roundtrip per engine. The time this happens at is unpredictable.

The benefit of saving memory might not always be worth the bandwidth cost.

Dominant language
Python
Stars
5
Forks
1
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from enthought/distarray

All issues in enthought/distarray

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.