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 a new page into the new-session-dialog. #1107

Closed
agatha197 opened this issue Aug 24, 2021 · 1 comment
Closed

Add a new page into the new-session-dialog. #1107

agatha197 opened this issue Aug 24, 2021 · 1 comment
Labels
area:ux UI / UX issue. effort:easy Need to understand only a specific region of codes (good first issue, easy). type:enhance Add new features
Milestone

Comments

@agatha197
Copy link
Contributor

Is your feature request related to a problem? Please describe.
There is an opinion that the number of sessions and the size of clusters are confusing.
So, I recommend you add a new page within the new-session-dialog and put those options on the new page.

Describe the solution you'd like
Make the structure of new-session-dialog as follows.

[1, 2 page]

  • No change

[3 page]

  • Resource Group
  • Resource allocation
    • CPU
    • RAM
    • Shared Memory
    • GPU
    • Sessions
  • Cluster mode
  • Cluster size
  • Session owner

[4 page]

  • Advanced settings
    • Session owner
    • Sessions
    • OMP_NUM_THREAD* (with information dialog)

[5 page]

  • Existing page 4
    (Total resource allocation, mounted folder, configurations, ...)

*OMP_NUM_THREAD
Backend.AI pre-specifies the OMP_NUM_THREADS environment variable as the number of allocated CPU cores in order to ensure that legacy software accurately recognizes container-allocated CPU resources while ensuring optimal performance when working with multi-threading through OpenMP. The pytorch official performance tuning guide also informs that it is necessary to adjust the value of OMP_NUM_THREAD when performing parallel operations as follows. https://pytorch.org/tutorials/recipes/recipes/tuning_guide.html#utilize-openmp

Describe alternatives you've considered
OMP_NUM_THREAD can actually be set in Environment Variable on page 1. I purposely added the OMP_NUM_THREAD option on page 4 because it seems likely that it often occurs when code for a distributed container environment is run on multiple cores within a single container. But you can add it wherever you think it is better.
So if you have a better idea to add the OMP_NUM_THREAD option to a better place, don't hesitate to share your ideas.

Additional context
You can save OMP_NUM_THREAD options like other environment variables on the first page.

@agatha197 agatha197 added type:enhance Add new features good first issue area:ux UI / UX issue. labels Aug 24, 2021
@agatha197 agatha197 added this to the 21.09 milestone Aug 24, 2021
@lizable
Copy link
Contributor

lizable commented Jan 19, 2022

Resolved via #1009.

@lizable lizable closed this as completed Jan 19, 2022
@inureyes inureyes added effort:easy Need to understand only a specific region of codes (good first issue, easy). and removed effort:1 labels Mar 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:ux UI / UX issue. effort:easy Need to understand only a specific region of codes (good first issue, easy). type:enhance Add new features
Projects
None yet
Development

No branches or pull requests

3 participants