Is your feature request related to a problem? Please describe.
In the current implementation of the extension, there are too many queries to the remote filesystem to check for things like - islink, isdir or isfile(ref). These requests add up and significantly slow down the interactions with the UI.
As can be seen in the logs, it takes 1 min for the FTP server to respond with all the information and while this happens, all other requests are blocked while the jupyter server queries the FTP server -
Describe the solution you'd like
I would like if something can be done to have fewer queries with the file system or if there is some other recommendation about using this extension.
Describe alternatives you've considered
I've tried the ssh protocol as well and it has the same problem.
Is your feature request related to a problem? Please describe. In the current implementation of the extension, there are too many queries to the remote filesystem to check for things like -
islink
,isdir
orisfile
(ref). These requests add up and significantly slow down the interactions with the UI.Here are logs from the FTP Server
``` [D 2022-06-30 07:30:54] 10.240.172.37:43252-[anonymous] <- MLSD / [D 2022-06-30 07:30:54] 10.240.172.37:43252-[anonymous] -> 125 Data connection already open. Transfer starting. [D 2022-06-30 07:30:54] [debug] starting transfer using send() (As can be seen in the logs, it takes 1 min for the FTP server to respond with all the information and while this happens, all other requests are blocked while the jupyter server queries the FTP server -
Describe the solution you'd like I would like if something can be done to have fewer queries with the file system or if there is some other recommendation about using this extension.
Describe alternatives you've considered I've tried the ssh protocol as well and it has the same problem.