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

Test performance of odo with large project #5830

Open
feloy opened this issue Jun 15, 2022 · 1 comment
Open

Test performance of odo with large project #5830

feloy opened this issue Jun 15, 2022 · 1 comment
Labels
area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering kind/task Issue is actionable task lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.

Comments

@feloy
Copy link
Contributor

feloy commented Jun 15, 2022 •
edited
Loading

/kind feature

Which functionality do you think we should add?

It would be interesting to test the performance of odo (essentially the odo dev command) with large projects (lots of files to synchronize, lots of dependencies, long compilation time, etc) to check that odo is able to handle such situation with acceptable delays
@openshift-ci openshift-ci bot added the kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation label Jun 15, 2022
@rm3l rm3l mentioned this issue Jun 28, 2022
Closed
@valaparthvi valaparthvi added the area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering label Jul 7, 2022
@rm3l rm3l mentioned this issue Aug 8, 2022
Closed
3 tasks
@anandrkskd anandrkskd self-assigned this Sep 1, 2022
@anandrkskd anandrkskd removed this from odo v3-beta2 Sep 1, 2022
@anandrkskd anandrkskd moved this to For Consideration in odo v3.0.0 Sep 1, 2022
@rm3l rm3l added this to odo Project Oct 3, 2022
@kadel kadel added kind/task Issue is actionable task and removed kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation labels Feb 20, 2023
@anandrkskd anandrkskd added the priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done. label Feb 21, 2023
@github-actions
Copy link
Contributor

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

@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 Oct 30, 2023
@rm3l rm3l added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering kind/task Issue is actionable task lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done.
Projects
odo Project
Status: No status
odo v3.0.0
Status: For Consideration
Milestone
No milestone
Development

No branches or pull requests
5 participants
@kadel @rm3l @feloy @valaparthvi @anandrkskd