cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

job init takes longer than notebook run

darshan
New Contributor III

I am trying to understand why running a job takes longer than running the notebook manually.

And if I try to run jobs concurrently using workflow or threads then is there a way to reduce job init time ?

3 REPLIES 3

Kaniz_Fatma
Community Manager
Community Manager

Hi @darshan doshiโ€‹, Are you using the same cluster for notebook and job runs?

Vivian_Wilfred
Honored Contributor

Hi @darshan doshiโ€‹ , Jobs creates a job cluster in the backend before it starts the task execution and this cluster creation may take extra time when compared to running a notebook on a existing cluster.

1) If you run a multi-task job, you could select the same cluster for all the tasks to reduce job initialization time.

2) You can also use an interactive cluster for the job tasks. Interactive clusters can be kept "on" during your job run schedules so that all the job runs can quickly use the interactive cluster to execute the tasks.

Hope this helps ๐Ÿ™‚

Hi @darshan doshiโ€‹,

Just a friendly follow-up. Did you saw the response from Vivian's? do you have any follow-up questions? lets us know if you still need help.

Connect with Databricks Users in Your Area

Join a Regional User Group to connect with local Databricks users. Events will be happening in your city, and you wonโ€™t want to miss the chance to attend and share knowledge.

If there isnโ€™t a group near you, start one and help create a community that brings people together.

Request a New Group