Skip to main content

Daskathon

Build Status Gitential Coding Hours

Deploy dask-worker processes on Marathon in response to load on a Dask scheduler. This creates a Marathon application of dask-worker processes. It watches a Dask Scheduler object in the local process and, based on current requested load, scales the Marathon application up and down.

Run

It’s not yet clear how to expose all of the necessary options to a command line interface. For now we’re doing everything manually.

Make an IOLoop running in a separate thread:

with MarathonCluster(marathon='http://localhost:8080',
                     cpus=1, mem=512, adaptive=True) as mc:
    with Client(mc.scheduler_address) as c:
        x = c.submit(lambda x: x + 1, 1)
        assert x.result() == 2

Create a Client and submit work to the scheduler. Marathon will scale workers up and down as neccessary in response to current workload.

from distributed import Client
c = Client(s.address)

future = c.submit(lambda x: x + 1, 10)

TODO

  • [x] Deploy the scheduler on the cluster

  • [x] Support a command line interface

Docker Testing Harness

This sets up a docker cluster of one Mesos master and two Mesos agents using docker-compose.

Requires:

  • docker version >= 1.11.1

  • docker-compose version >= 1.7.1

docker-compose up

Run py.test:

py.test dask-marathon

Web UIs

History

Dask-marathon originally forked from https://github.com/mrocklin/dask-marathon

Metadata

Release files for daskathon 1.3.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for daskathon 1.3.1
File Size Uploaded Provenance Actions
daskathon-1.3.1.tar.gz 23.3 kB Without provenance Details for daskathon-1.3.1.tar.gz

Release files / daskathon-1.3.1.tar.gz

Download URL daskathon-1.3.1.tar.gz
Size 23.3 kB
Tags Source
SHA-256 checksum
How to use checksums
1dfb096965e61337d0825ba578c787acd50022de5e96c31ee0a4cf4a82835f70
BLAKE2b-256 checksum
How to use checksums
793ede77ae23ae88d4ab03c5f0575316987d3e758a824d914c2a12bc1805c22a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for daskathon 1.3.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page