Skip to content

Conversation

@amogkam
Copy link
Contributor

@amogkam amogkam commented Mar 21, 2023

Why are these changes needed?

Related issue number

Checks

Signed-off-by: amogkam <[email protected]>
@amogkam amogkam changed the title [data] [wip] introduce zero copy [data] [wip] zero copy batch format Mar 21, 2023
amogkam added 3 commits March 21, 2023 11:46
Signed-off-by: amogkam <[email protected]>
Signed-off-by: amogkam <[email protected]>
Signed-off-by: amogkam <[email protected]>
@ericl ericl self-assigned this Mar 21, 2023
@ericl ericl closed this Mar 22, 2023
ericl added a commit that referenced this pull request Mar 22, 2023
…es in the current batch format with zero copies (#33562)

This PR is a cleanup of #33536

It uses "None" instead of "zero-copy" as a batch format, since None has a similar meaning for batch_size, where it means a system-chosen batch size. Here "None" also means the system chosen optimal batch format.
elliottower pushed a commit to elliottower/ray that referenced this pull request Apr 22, 2023
…es in the current batch format with zero copies (ray-project#33562)

This PR is a cleanup of ray-project#33536

It uses "None" instead of "zero-copy" as a batch format, since None has a similar meaning for batch_size, where it means a system-chosen batch size. Here "None" also means the system chosen optimal batch format.

Signed-off-by: elliottower <[email protected]>
ProjectsByJackHe pushed a commit to ProjectsByJackHe/ray that referenced this pull request May 4, 2023
…es in the current batch format with zero copies (ray-project#33562)

This PR is a cleanup of ray-project#33536

It uses "None" instead of "zero-copy" as a batch format, since None has a similar meaning for batch_size, where it means a system-chosen batch size. Here "None" also means the system chosen optimal batch format.

Signed-off-by: Jack He <[email protected]>
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