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.

Sign up for GitHub

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

Jump to bottom

Compute PV size for tuple transfer #8

Open
strieflin opened this issue Dec 16, 2022 · 3 comments
Open

Compute PV size for tuple transfer #8

strieflin opened this issue Dec 16, 2022 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@strieflin
Copy link
Member

The size of the persistent volume used to transfer generated tuples from the generator to the provisioner is currently hardcoded. A better approach would be to compute the required size from the number of tuples that are to be generated.
@strieflin strieflin added priority/backlog Higher priority than priority/awaiting-more-evidence. kind/feature Categorizes issue or PR as related to a new feature. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Dec 16, 2022
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Dec 16, 2022
@strieflin strieflin mentioned this issue Dec 16, 2022
Merged
@strieflin strieflin removed the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jan 23, 2023
@github-actions
Copy link

This issue has been marked stale because it has been open for 90 days with no activity. It will be automatically closed in 30 days if no further activity occurs.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 24, 2023
@sbckr sbckr removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 2, 2023
@github-actions
Copy link

github-actions bot commented Aug 1, 2023

This issue has been marked stale because it has been open for 90 days with no activity. It will be automatically closed in 30 days if no further activity occurs.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 1, 2023
@github-actions
Copy link

github-actions bot commented Sep 1, 2023

This issue has been closed because it has been stale for 30 days.

@github-actions github-actions bot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Sep 1, 2023
@github-actions github-actions bot closed this as completed Sep 1, 2023
@strieflin strieflin removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 1, 2023
@strieflin strieflin reopened this Sep 1, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Sep 1, 2023
@strieflin strieflin removed the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Sep 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@strieflin @sbckr