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
If you have a large number of files in a git repo, jupyterlab-git makes all of lab slow/unresponsive.
While I am not sure of what should define large nor how the status of each file is taken into account, I have included a reproducer below as a starter. This issue was found when someone had a spurious .git in a home directory making lab unresponsive, but things like node_modules can sometimes have this number of files.
While there are a lot of possible fixes, one ideas during the request to somewhat specify what you think the state of the world is and the backend only sends the diff.
Reproduce
Create a new directory and run:
git init
for n in {1..10000}; do touch $n.txt; done
Navigate to that directory in lab. Play around and you'll notice lab becomes unusable. If lab still works fast, crank up n above.
Expected behavior
Git should not slow down lab.
Context
[email protected]
Chrome Version 86.0.4240.75 (Official Build) (64-bit)
The text was updated successfully, but these errors were encountered:
While there are a lot of possible fixes, one ideas during the request to somewhat specify what you think the state of the world is and the backend only sends the diff.
fwiw the main culprit seemed to be rendering 1000s of dom nodes when creating the untracked files list see #667 (comment)
Description
If you have a large number of files in a git repo, jupyterlab-git makes all of lab slow/unresponsive.
While I am not sure of what should define large nor how the status of each file is taken into account, I have included a reproducer below as a starter. This issue was found when someone had a spurious
.git
in a home directory making lab unresponsive, but things likenode_modules
can sometimes have this number of files.While there are a lot of possible fixes, one ideas during the request to somewhat specify what you think the state of the world is and the backend only sends the diff.
Reproduce
Create a new directory and run:
Navigate to that directory in lab. Play around and you'll notice lab becomes unusable. If lab still works fast, crank up
n
above.Expected behavior
Git should not slow down lab.
Context
[email protected]
Chrome Version 86.0.4240.75 (Official Build) (64-bit)
The text was updated successfully, but these errors were encountered: