Skip to content

[Data] Streamline concurrency parameter semantic #56422

@alexeykudinkin

Description

@alexeykudinkin

What happened + What you expected to happen

Context

This parameter is already overloaded with semantic, let's actually simplify it and make it consistent across Task/Actor pools:

Proposed Changes

  • Single int concurrency should just be max_concurrency (for both Tasks and Actors)

  • By default all Task/Actor Pools are autoscaling (ie [0, max_concurrency])

  • We add additional param/config to disable autoscaling for Actor Pools (which will then make Actor Pools have exactly max_concurrency actors)

  • Instead of providing a tuple we'd just expose individual params min/max/initial_op_concurrency

Versions / Dependencies

NA

Reproduction script

NA

Issue Severity

None

Metadata

Metadata

Assignees

Labels

P1Issue that should be fixed within a few weeksbugSomething that is supposed to be working; but isn'tdataRay Data-related issuesenhancementRequest for new feature and/or capability

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions