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

Non-mandatory tour scheduling model runtime gets worse as more multiprocess cores are added #25

Open
jpn-- opened this issue Jul 18, 2024 · 0 comments
Open

Non-mandatory tour scheduling model runtime gets worse as more multiprocess cores are added #25

jpn-- opened this issue Jul 18, 2024 · 0 comments

Comments

@jpn--
Copy link
Member

jpn-- commented Jul 18, 2024

As seen by @i-am-sijia in #9 (comment) and @dhensle in #9 (comment), the non-mandatory tour scheduling model runtime gets worse as more multiprocess cores are added. This is not seen in the sharrow on version of the code, only in the legacy code.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jpn--