fastmap 0.0.3

Fastmap is a drop-in replacement for `map` that parallelizes your code on the cloud.

Note: Fastmap is currently in beta.

Simple distributed computing

Fastmap is a drop-in replacement for map that makes your Python code in parallel on the cloud.

Fastmap is appropriate to use when map is too slow but setting up infrastracture would be overkill.

• 🚀 Speed up your code. Fastmap automatically parallelizes your code and distributes work across both your local machine and the fastmap cloud service. If the cloud won't speed things up, fastmap will do all processing locally and you won't be charged.
• 🐣 Trivial to setup. Get an API token, add global_init to the top of your file, and replace every instance of map with fastmap. There are no servers to provision or code to upload. The SDK consists of only 3 functions.
• 💵 Cheaper than you think. When you signup, you can get 1000 fastmap credits for free. That's enough for 100 vCPU-hours of processing or 100GB egress. Additional credits are $10 for 1000.
• 🧟‍♂️ Continuity plan. You depend on fastmap. If for any reason, in the future, fastmap.io must shut down, everything will be open-sourced.

Docs

For complete documentation, go to https://fastmap.io/docs,

Installation

pip install fastmap

Quickstart

import csv
from config import FASTMAP_TOKEN
from my_project import big_function
import fastmap

# Important: Protect your API token like a password and never commit it to version control
config = fastmap.init(secret=FASTMAP_TOKEN)

with open('lots_of_data.csv') as fh:
    long_list = list(csv.reader(fh))

results = list(config.fastmap(big_function, long_list))

When should you use fastmap?

As a rule-of-thumb, fastmap will speed up any call to map that would have otherwise taken more than one second. This is possible because, under the default ADAPTIVE execution policy, fastmap algorithmically distributes work between local execution and the fastmap.io cloud service.

If you are planning to use the 'CLOUD' exec_policy, which prevents local processing, fastmap is appropriate when your function is computationally-heavy. This is because transferring data to the cloud for processing always takes a non-zero amount of time. The tradeoff depends on your network speeds and distance to the fastmap server cluster (GCP: US-Central1).

If in doubt, try running fastmap with a small test dataset. Fastmap attempts to be transparent and will inform you when using it has made your code slower.

Questions

Fastmap.io is a new project and I would love to hear your feedback. You can contact me directly at [e-mail].