Change naming conventions for cores and memory
See original GitHub issueCurrently cluster objects in this project take in keywords like the following:
cluster = FooCluster(threads=4, processes=8, memory="16GB")
Where threads means threads-per-process and memory means memory-per-process.
However, I suspect that changing the meaning of these terms to the following might be more intuitive for users and administrators:
cluster = FooCluster(cores=32, processes=8, memory="128GB")
This would be a breaking change, but given how small and well connected the current user base is this seems doable.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:9 (9 by maintainers)
Top Results From Across the Web
What naming conventions do you follow with functions that ...
Routines that allocate, manage, or take responsibility for storage have special names and abide by the following guidelines: Routines that make ...
Read more >Intel® Processor Names, Numbers and Generation List
Understanding Intel® Processor Naming Conventions: The processor number is just one of several factors—along with processor brand, system configurations, ...
Read more >Naming Standards - The Philosophy of FileMaker
Core Solutions has published naming conventions since 1999, even predating FileMaker, Inc., in an effort to share the efficiencies they've realized over the ......
Read more >Assign CPU Resources to Containers and Pods - Kubernetes
This page shows how to assign a CPU request and a CPU limit to a container. Containers cannot use more CPU than the...
Read more >Naming convention (programming) - Wikipedia
In computer programming, a naming convention is a set of rules for choosing the character sequence to be used for identifiers which denote...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Also a bit tangential but I have to say that when reading the
dask-worker --help
about--memory-limit
, I would have guessed that--memory-limit
is about thedask-worker
memory limit and not a per-process memory limit.Closed thanks to #86.