You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am using Kedro 18.14 on Databricks 11.4 LTS. I am trying to run kedro as suggested in documentation and using %reload_kedro to refresh session. However, it takes more than 2 mins for this command to finish. Is this expected behaviour?
Context
Slow run time
Steps to Reproduce
Create Databricks compute with 11.3 machine
Install kedro 18.14 in the notebook
Add a kedro project to workspace using the git repository option on Databricks
Try to load kedro project using %reload_kedro magic
Expected Result
The reload magic should be fast, a few seconds probably
Actual Result
Your Environment
Kedro version used (pip show kedro or kedro -V): 18.14
Python version used (python -V): 3.9
Operating system and version: Databricks (details in image below)
The text was updated successfully, but these errors were encountered:
Sorry for the late response, @sagrawal128 How big is the project? Is the setup very heavy that it takes a lot of time? During %reload_kedro, Kedro basically try to create
DataCatalog
Pipeline
ConfigLoader
These are all components that is necessary before a pipeline run, usually they should be fast. It would be also good to check what kind of dataset are you using, if possible upgrade kedro-datasets. There were issue with some older dataset that setup a database connection early which is causing performance issue.
Description
Hi, I am using Kedro 18.14 on Databricks 11.4 LTS. I am trying to run kedro as suggested in documentation and using
%reload_kedro
to refresh session. However, it takes more than 2 mins for this command to finish. Is this expected behaviour?Context
Slow run time
Steps to Reproduce
%reload_kedro
magicExpected Result
The reload magic should be fast, a few seconds probably
Actual Result
Your Environment
pip show kedro
orkedro -V
): 18.14python -V
): 3.9The text was updated successfully, but these errors were encountered: