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

Validate maximum number of workers for flux #527

Merged
merged 3 commits into from
Dec 20, 2024
Merged

Conversation

jan-janssen
Copy link
Member

@jan-janssen jan-janssen commented Dec 20, 2024

Summary by CodeRabbit

  • New Features

    • Introduced a validation function for maximum worker allocation to enhance resource management.
    • Updated executor functionality to include compatibility checks for resource allocation.
  • Bug Fixes

    • Enhanced the validation process to ensure that errors are raised for invalid resource configurations.
  • Tests

    • New test case added to validate the behavior of the executor with respect to resource limits.

Copy link
Contributor

coderabbitai bot commented Dec 20, 2024

Walkthrough

The pull request introduces a new resource validation mechanism for the Flux allocation backend in the executor library. A new function validate_max_workers is added to executorlib/interactive/flux.py to check the compatibility of requested workers with available system cores. The create_executor function is updated to incorporate this validation, ensuring that resource allocation adheres to system constraints when block_allocation is enabled. The changes enhance resource management and prevent over-allocation of computational resources.

Changes

File Change Summary
executorlib/interactive/executor.py Updated create_executor function to include resource validation for max_workers in the Flux backend.
executorlib/interactive/flux.py Added new validate_max_workers function to check core allocation limits based on max_workers, cores, and threads_per_core.
tests/test_executor_backend_flux.py Added test_validate_max_workers method to verify that a ValueError is raised when resource limits are exceeded.

Sequence Diagram

sequenceDiagram
    participant User
    participant CreateExecutor
    participant FluxValidation
    participant SystemResources

    User->>CreateExecutor: Request executor with max_workers
    CreateExecutor->>FluxValidation: Validate max_workers
    FluxValidation->>SystemResources: Check available cores
    alt Cores sufficient
        FluxValidation-->>CreateExecutor: Validation passed
        CreateExecutor-->>User: Create Executor
    else Insufficient cores
        FluxValidation-->>CreateExecutor: Raise ValueError
        CreateExecutor-->>User: Resource allocation error
    end
Loading

Possibly related PRs

Poem

🐰 In the realm of cores and threads so bright,
A rabbit hops with validation's might!
Max workers checked with careful grace,
No resource wasted in this coding space.
Flux backend sings a balanced song! 🚀


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 14c9381 and 94c0d8e.

📒 Files selected for processing (1)
  • executorlib/interactive/executor.py (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • executorlib/interactive/executor.py

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
tests/test_executor_backend_flux.py (1)

117-125: Consider adding more test cases for comprehensive validation.

While the current test verifies the basic validation scenario, consider adding these test cases:

  • Edge case where requested cores equal available cores (should pass)
  • Case with minimal values (e.g., 1 core, 1 thread)
  • Case with non-default thread counts

Example addition:

 def test_validate_max_workers(self):
     with self.assertRaises(ValueError):
         Executor(
             max_workers=10,
             resource_dict={"cores": 10, "threads_per_core": 10},
             flux_executor=self.executor,
             backend="flux_allocation",
             block_allocation=True,
         )
+    # Should pass: Equal to available cores
+    Executor(
+        max_workers=1,
+        resource_dict={"cores": 1, "threads_per_core": 1},
+        flux_executor=self.executor,
+        backend="flux_allocation",
+        block_allocation=True,
+    )
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b37acd6 and 14c9381.

📒 Files selected for processing (3)
  • executorlib/interactive/executor.py (2 hunks)
  • executorlib/interactive/flux.py (1 hunks)
  • tests/test_executor_backend_flux.py (1 hunks)
🔇 Additional comments (1)
executorlib/interactive/executor.py (1)

229-233: Consider validating resources regardless of block_allocation.

The current implementation only validates resources when block_allocation=True. This could potentially lead to resource overallocation when block_allocation=False.

Let's verify if there are any existing resource checks for non-block allocation:

Consider:

  1. Moving the validation earlier in the function, before other resource-specific checks
  2. Implementing validation for non-block allocation cases
  3. Adding a comment explaining why validation is only needed for block allocation if that's intentional

Comment on lines +10 to +20
def validate_max_workers(max_workers, cores, threads_per_core):
handle = flux.Flux()
cores_total = flux.resource.list.resource_list(handle).get().up.ncores
cores_requested = max_workers * cores * threads_per_core
if cores_total < cores_requested:
raise ValueError(
"The number of requested cores is larger than the available cores "
+ str(cores_total)
+ " < "
+ str(cores_requested)
)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Improve error handling and type safety.

The validation function could benefit from the following improvements:

  1. Use f-strings for better readability
  2. Add type hints
  3. Ensure proper resource cleanup

Consider this implementation:

-def validate_max_workers(max_workers, cores, threads_per_core):
+def validate_max_workers(max_workers: int, cores: int, threads_per_core: int) -> None:
     handle = flux.Flux()
-    cores_total = flux.resource.list.resource_list(handle).get().up.ncores
-    cores_requested = max_workers * cores * threads_per_core
-    if cores_total < cores_requested:
-        raise ValueError(
-            "The number of requested cores is larger than the available cores "
-            + str(cores_total)
-            + " < "
-            + str(cores_requested)
-        )
+    try:
+        cores_total = flux.resource.list.resource_list(handle).get().up.ncores
+        cores_requested = max_workers * cores * threads_per_core
+        if cores_total < cores_requested:
+            raise ValueError(
+                f"The number of requested cores is larger than the available cores: "
+                f"{cores_total} < {cores_requested}"
+            )
+    finally:
+        handle.close()
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
def validate_max_workers(max_workers, cores, threads_per_core):
handle = flux.Flux()
cores_total = flux.resource.list.resource_list(handle).get().up.ncores
cores_requested = max_workers * cores * threads_per_core
if cores_total < cores_requested:
raise ValueError(
"The number of requested cores is larger than the available cores "
+ str(cores_total)
+ " < "
+ str(cores_requested)
)
def validate_max_workers(max_workers: int, cores: int, threads_per_core: int) -> None:
handle = flux.Flux()
try:
cores_total = flux.resource.list.resource_list(handle).get().up.ncores
cores_requested = max_workers * cores * threads_per_core
if cores_total < cores_requested:
raise ValueError(
f"The number of requested cores is larger than the available cores: "
f"{cores_total} < {cores_requested}"
)
finally:
handle.close()

@jan-janssen jan-janssen merged commit 44214f7 into main Dec 20, 2024
27 checks passed
@jan-janssen jan-janssen deleted the validate_flux branch December 20, 2024 00:16
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.

1 participant