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 ability to specify maxSwap for ECS clusters #59

Open
gvelchuru opened this issue Jan 28, 2020 · 1 comment
Open

Add ability to specify maxSwap for ECS clusters #59

gvelchuru opened this issue Jan 28, 2020 · 1 comment
Labels
enhancement New feature or request help wanted Extra attention is needed provider/aws/ecs Cluster provider for AWS ECS

Comments

@gvelchuru
Copy link
Contributor

It would be nice to specify swap memory, especially when dealing with very large DataFrames

https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html#container_definitions (search for maxSwap)

@jacobtomlinson
Copy link
Member

jacobtomlinson commented Jan 29, 2020

I would be happy to explore this but it is worth noting that Dask manages it's own memory swapping and doesn't use the built in system swap. Futures are moved in and out of memory into the temporary worker space on disk.

If you are having trouble with workers running out of memory this may be related to your dataframe partitioning.

@jacobtomlinson jacobtomlinson added enhancement New feature or request help wanted Extra attention is needed provider/aws/ecs Cluster provider for AWS ECS labels Dec 16, 2020
lukaszo pushed a commit to lukaszo/dask-cloudprovider that referenced this issue Oct 12, 2023
Changes by create-pull-request action
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed provider/aws/ecs Cluster provider for AWS ECS
Projects
None yet
Development

No branches or pull requests

2 participants