yongkangchen / remote-sync

Upload your files to remote host after every change. Both SCP/SFTP and FTP are supported.
https://atom.io/packages/remote-sync
MIT License
237 stars 71 forks source link

VERY SLOW: Updating Atom and Remote-sync to the latest versions #452

Open ryan-ajmadison opened 6 years ago

ryan-ajmadison commented 6 years ago

I recently updated both my Atom and the Remote-sync package to the latest versions and now I'm bogged down. Switching tabs has a delay, typing is delayed and uploading to remote on save takes about twice as long. If I turn remote sync off, Atom works fine. Please help, majorly affecting work flow.

daverickdunn commented 6 years ago

You should try reinstalling / rebuilding the package if you haven't already. I haven't seen this issue personally so can't really comment on what may be causing it.

ryan-ajmadison commented 6 years ago

Do you have the most recent versions of both Atom and the package? If not, can you share what version you're using for both? I'd gladly revert to an earlier version if I can prevent the slowness.

daverickdunn commented 6 years ago

Latest for both... Which OS are you using?

ryan-ajmadison commented 6 years ago

I have latest for everything, and the latest OSx. I've discovered that it seems to be caused by my watch directive. I've been using this for the last 6 months, and I've just been watching the main directory, "/", but suddenly that seems to be the problem now. If I change watch to a sub directory, it works great again, so it's on my end possibly? Suggestions on how to watch my entire project without slowing it down that much?

ryan-ajmadison commented 6 years ago

This has been resolved, the issue was on my end. Trying to watch the entire project, but too many files. I ignored the biggest offenders and it resolved the issue. Thanks.

daverickdunn commented 6 years ago

Thanks for the info. The package for file monitoring, chokidar, has a few other edge-case issues as well. I'll take a look at updating it soon as I think remote-sync is using a fairly old version.

ryan-ajmadison commented 6 years ago

I'm actually back to square one on this, it worked for about 20 minutes, and now it's broken again. My project is large, so when I set 'watch' to '/' it freezes up and my CPU on my MacBook Pro shoots up to 192.8. If I choose only one of the directories, it's much better. As I mentioned before, I tried ignoring the big offenders in my project, but it doesn't seem to be working anymore.

Any recommendations on how to watch an entire project?

daverickdunn commented 6 years ago

How large are we talking here? Can you do a file/folder count? Are you tracking things like npm _nodemodules folders, because they become insanely large very quickly...