Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

~2 second delay to get explorer window; files accessed over sshfs #67

Open
slisznia opened this issue Nov 4, 2017 · 4 comments
Open

Comments

@slisznia
Copy link

slisznia commented Nov 4, 2017

OS: Linux / Ubuntu 16.04

I'm experiencing a delay of about two seconds from the time I'm requesting the explorer to the time the buffer-selection window comes up. This applies only when the files (buffers) are accessed over the sshfs mount (I haven't tried NFS). The number of open files does not matter - i.e. as few as 2 files in the selection window.

When I'm doing :ls the buffers are listed instantaneously.

It seems that there is some sort of file-checking every time the Explorer is requested, which requires a network round-trip.

@slisznia slisznia changed the title ~2 second delay when opened files are mounted remotely ~2 second delay when requesting explorer, files accessed over sshfs Nov 4, 2017
@slisznia slisznia changed the title ~2 second delay when requesting explorer, files accessed over sshfs ~2 second delay to get explorer window; files accessed over sshfs Nov 4, 2017
@jlanzarotta
Copy link
Owner

jlanzarotta commented Nov 6, 2017

Hum... I will check into this... thanks...

@jlanzarotta
Copy link
Owner

Okay... this is interesting. I believe I can reproduce this on windows also...

@slisznia
Copy link
Author

slisznia commented Nov 6, 2017

Btw, this isn't something new. I've seen the lag since at least v7.4.2 until now, v7.4.19. Finally got the courage to mention it because the plugin is nothing short of amazing.

@jlanzarotta
Copy link
Owner

Thanks for using bufexplorer. Sorry for the hassles it has given you right now.

I do not work with networked files very often so I have not seen this before.

Do not hesitate in the future to point out something that is wrong. I may or may not be able to fix it; however, there are lots of people who monitor this plugin, so someone is bound to figure out a solution :)

As of now, it looks like something in the GetBufferInfo() method. When I test the plugin with a networked file, I am seeing timing similar to what you are getting. Not sure what the culprit is thought...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants