Skip to content
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

Add docstrings for new stream class, update sphinx docs #44

Merged
merged 7 commits into from
Jan 25, 2024

Conversation

amitschang
Copy link
Member

@amitschang amitschang commented Jan 25, 2024

Adding some docstrings for new classes and methods. Also subbing out some pages for the manual.

Copy link

codecov bot commented Jan 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (05b00bb) 100.00% compared to head (53f2768) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #44   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           11        11           
  Lines          551       551           
=========================================
  Hits           551       551           
Flag Coverage Δ
unittests 100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@amitschang amitschang marked this pull request as ready for review January 25, 2024 17:42
@amitschang amitschang requested a review from a team as a code owner January 25, 2024 17:42
@amitschang amitschang requested review from SamuelCarliles3 and jamienoss and removed request for SamuelCarliles3 January 25, 2024 17:42
Copy link
Member

@jamienoss jamienoss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍
Just some typos and the possibility of mentioning that resources are overcommitted.

for execution, until yeilded by :meth:`run`, where they are de-serialized on
the driver.

This executor will attempt to pack the cluster, irrespective of any other
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should somewhere mention that we not just packing but overcommitting?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think that is necessary, it utilizes the ray scheduler to make sure tasks are run. The mention above is just to say that it does not consider any other workloads.

already been initialized

Args:
ray_poll_timeout: After scheduling as many tasks as can fit, ray.wait on
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should somewhere mention that we not just packing but overcommitting?

Like maybe (also) here 🤷 ?

amitschang and others added 6 commits January 25, 2024 15:23
Co-authored-by: Jamie Noss <jnoss@jhu.edu>
Co-authored-by: Jamie Noss <jnoss@jhu.edu>
Co-authored-by: Jamie Noss <jnoss@jhu.edu>
Co-authored-by: Jamie Noss <jnoss@jhu.edu>
Co-authored-by: Jamie Noss <jnoss@jhu.edu>
Co-authored-by: Jamie Noss <jnoss@jhu.edu>
@amitschang
Copy link
Member Author

@jamienoss , thanks, I probably should have run a spell-checker - and I had no idea I had such a tendency to type yeilded 😆

@amitschang amitschang requested a review from jamienoss January 25, 2024 20:29
Copy link
Member

@jamienoss jamienoss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Though, I find it important info to know that a scheduler will overcommit such that I have a better handle on resource expectations. Maybe I should just always assume that everything overcommits.

@amitschang
Copy link
Member Author

Thanks. And to be clear, it doesn't overcommit in the sense that more tasks than resources run expecting that some will not use what they request. Ray will ensure that the resources requested are guaranteed for the task (e.g. if you have 8 cores and tasks using 5 and 4, both will not run at the same time)

@amitschang amitschang merged commit 77666ce into main Jan 25, 2024
12 checks passed
@amitschang amitschang deleted the docs-update branch January 25, 2024 20:45
@jamienoss
Copy link
Member

Ok, good to know - I guess I misunderstood a comment in #43 but never mind. Maybe I'm just misremembering it lol.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants