topic Re: Does Databricks supports the Pytorch Distributed Training for multiple devices? in Data Engineering

Does Databricks supports the Pytorch Distributed Training for multiple devices?

Smu_Tan — Wed, 13 Apr 2022 20:24:43 GMT

Hi, Im trying to use the databricks platform to do the pytorch distributed training, but I didnt find any info about this. What I expected is using multiple clusters to run a common job using pytorch distributed data parallel (DDP) with the code below:

On device 1: %sh python -m torch.distributed.launch --nproc_per_node=4 --nnodes=2 --node_rank=0 --master_addr="127.0.0.1" --master_port=29500 train_something.py

On device 2: %sh python -m torch.distributed.launch --nproc_per_node=4 --nnodes=2 --node_rank=1 --master_addr="127.0.0.1" --master_port=29500 train_something.py

This is definitely supported by other computation platform like slurm, but it failed in the databricks. Could you let me know whether you do support this? or you will consider to add this feature for the later developments. Thank you in advance!

Re: Does Databricks supports the Pytorch Distributed Training for multiple devices?

-werners- — Thu, 14 Apr 2022 14:12:50 GMT

@Shaomu Tan , can you check sparktorch?

The parallel processing on Databricks clusters is mainly based on Apache Spark™. So to use the parallel processing, the library in question (PyTorch) has to be written for Spark. spark torch is an attempt to do just that.

You can also run Apache Ray on Databricks or Dask (I thought that was possible too), so bypassing Apache spark

Re: Does Databricks supports the Pytorch Distributed Training for multiple devices?

axb0 — Sun, 19 Feb 2023 16:15:27 GMT

With Databricks MLR, HorovodRunner is provided which supports distributed training and inference with PyTorch. Here's an example notebook for your reference: PyTorchDistributedDeepLearningTraining - Databricks.

Re: Does Databricks supports the Pytorch Distributed Training for multiple devices?

adarsh8304 — Fri, 29 Nov 2024 10:04:13 GMT

Hey, so we even can't use the TorchDistributor and Distributed Data Parallel to achieve the distributed training thing in my code, and `TorchDistributor` is a spark written distribution library, coz with this setup I am not able to get the the required distributed training that expected .. second worker node have no ups in the metrics side. .. giving this reply more path, ^^ essentially how should we do the distributed training in a databricks multi node setup which have 1 driver with 1 worker. @-werners- @axb0 @Smu_Tan , should we move out of pytorch fully for this purpose or use a complete spark code to achieve this, or there's any dependancy which can provide help with this approach.

Re: Does Databricks supports the Pytorch Distributed Training for multiple devices?

-werners- — Fri, 29 Nov 2024 10:19:19 GMT

Since you replied on a rather old topic: TorchDistributor enables pytorch on spark in distributed mode.
But a cluster with only 1 worked and 1 driver will not run in distributed mode.
The driver does not execute spark tasks, it handles spark overhead and f.e. python code outside of spark.
If you want to run in distributed mode you should have at least 2 workers (and always a driver).

Re: Does Databricks supports the Pytorch Distributed Training for multiple devices?

adarsh8304 — Wed, 04 Dec 2024 07:18:51 GMT

Hey @-werners- thanks for answering first, why then the metrics of cpu, mem utilisation we are getting in driver only and worker seems still, with less utilisation of any training, with torch distributor I think atleast that one worker should be in use, right ?

one more thing, are the databricks driver machine designed in such a way that makes it less optimal and performant for the model training and inference tasks. as databricks implies that the code should be in apache spark only ( keeping pytorch and pandas out of execution line).

Re: Does Databricks supports the Pytorch Distributed Training for multiple devices?

-werners- — Wed, 04 Dec 2024 07:38:16 GMT

If only the driver is active, this probably means you are not using Spark. When running pure python,... code, the driver will execute that.
If Spark is active, workers receive their tasks from the driver. Generally the driver is not that active, the workers do all the work.The driver machine is not designed in any way. You can define yourself what kind of machine you use as a driver.
You can even run in single node mode, so you only have a driver (which also acts as a worker).