DASK so cool - Faster data analytics with Python and DASK - Run locally with Docker

Data scientists and others want to analyze and manipulate lots of data without having to be Software developers. Jupyter notebooks, Python and no DASK are vehicles that help make that happen.

 DASK is a distributed Python library that can run in pretty much any Python environment.  It was designed to help data scientists scale up their data analysis by providing an easy to use distributed compute API and paradigm. DASK/Python can be run both inside Jupyter notebooks and as standalone Python programs.

Environment

The DASK environment consists of a Dask Scheduler and any number of worker nodes. The Python program sends a set of tasks to the Dask Scheduler which then distributes those across the worker nodes.  The worker node results are then aggregated  and returned to the original program.

Docker

The DASK team provides samples how to use docker-compose to create a DASK development and execution environment The environment consists of
  • A development node with Python and Jupyter Notebook server
  • A DASK scheduler
  • DASK worker nodes
I have created a docker-compose.yml file  that mounts persistent storage on the development node. This makes it easy to keep work across container deployments.  My docker-compose.yml file is derived from the DASK team's examples which do not have persistent storage, at this time.

Local DASK docker cluster deployed in Docker


















Quickstart DASK Python Code

See this docker-scripts repository on GitHub. 
  1. Clone the repository, 
  2. cd into dask
  3. run docker-compose up.
  4. Run this sample code

from dask.distributed import Client
client = Client('scheduler:8786')
def square(x):
    return x ** 2
def neg(x):
    return -x


# this will run two different distributed operations
A = client.map(square, range(100))
B = client.map(neg, A)


total = client.submit(sum, B)
total.result()


client.gather(A)








DASK in Action



The demonstration code for the video came from distributed.dask.org quickstart



DASK with Jupyter notebooks running locally on Docker















DASK with VSCode running locally on Docker






















































Comments











Post a Comment






























Popular posts from this blog









Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached




















Image







I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Update Driver  does  not  install the RNDI








Read more










Understanding your WSL2  RAM and swap - Changing the default 50%-25%




















Image







The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up  or down  to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit.                                                  Click to Enlarge           The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaults to a maximum RAM size of 5








Read more










Almost PaaS Document Parsing with Tika and AWS Elastic Beanstalk




















Image







The Apache Tika project  provides a  library capable of parsing and extracting data and meta data from over 1000 file types.  Tika is available as a single jar file that can be included inside applications or as a deployable jar file that runs Tika as a standalone service.   This blog describes deploying the Tika jar as an auto-scale service in Amazon AWS Elastic Beanstalk.  I selected Elastic Beanstalk because it supports jar based deployments without any real Infrastructure configuration. Elastic Beanstalk auto-scale should take care of scaling up and down for for the number of requests you get.     Tika parses documents and extracts their text completely in memory. Tika was deployed for this blog using EC2 t2.micro instances available in the AWS free tier. t2.micro VMs are 1GB which means that you are restricted in document complexity and size. You would size your instances appropriately for your largest documents.     Preconditions    An AWS account.  AWS access id and secret key. 








Read more