Skip to content

Optimize getting run plan when using region/instance-type filters #1206

Closed

Description

@jvstme

Current

The user can filter instance offers by region or instance type, e.g.:

dstack run . --region westus3

However, the current implementation always prepares offers for all regions and instance types and applies the filters only after that. This may slow down getting the run plan significantly due to checking quotas and availability for the instances that will then be filtered out.

Proposed

Pass these filters to Compute.get_offers and adjust backend implementations to only prepare offers for the requested regions and instance types.

Activity

  1. peterschmidt85 commented on Jun 9, 2024

    @peterschmidt85
    Contributor

    This issue is stale because it has been open for 30 days with no activity.

  2. peterschmidt85 commented on Jun 24, 2024

    @peterschmidt85
    Contributor

    This issue was closed because it has been inactive for 14 days since being marked as stale. Please reopen the issue if it is still relevant.

  3. jvstme commented on Jun 24, 2024

    @jvstme
    CollaboratorAuthor

    Relevant

  4. reopened this on Jun 24, 2024
  5. peterschmidt85 commented on Jul 25, 2024

    @peterschmidt85
    Contributor

    This issue is stale because it has been open for 30 days with no activity.

  6. github-actions commented on Aug 9, 2024

    @github-actions

    This issue was closed because it has been inactive for 14 days since being marked as stale. Please reopen the issue if it is still relevant.

  7. reopened this on Aug 9, 2024
  8. github-actions commented on Sep 9, 2024

    @github-actions

    This issue is stale because it has been open for 30 days with no activity.

  9. 18 remaining items

  10. github-actions commented on Mar 13, 2025

    @github-actions

    This issue was closed because it has been inactive for 14 days since being marked as stale. Please reopen the issue if it is still relevant.

  11. reopened this on Mar 14, 2025
  12. github-actions commented on Apr 21, 2025

    @github-actions

    This issue is stale because it has been open for 30 days with no activity.

  13. github-actions commented on May 5, 2025

    @github-actions

    This issue was closed because it has been inactive for 14 days since being marked as stale. Please reopen the issue if it is still relevant.

  14. r4victor commented on May 5, 2025

    @r4victor
    Collaborator

    The same optimization can be applied to backends when a compute can return offers for multiple backends as in dstack Sky.

  15. r4victor commented on Sep 17, 2025

    @r4victor
    Collaborator

    Not relevant after #3091

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions