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

rshell takes too much time to communicate #158

Open
pulkin opened this issue May 9, 2021 · 2 comments
Open

rshell takes too much time to communicate #158

pulkin opened this issue May 9, 2021 · 2 comments

Comments

@pulkin
Copy link

pulkin commented May 9, 2021

My rsync, for example, takes 40 seconds or so with a very few folders. Partially because every single remote command resets the module and re-compiles (small) chunks of code.

@davehylands
Copy link
Collaborator

Yep - I agree. When I originally wrote rshell, it was only running with the pyboard, which has a direct USB connection. MCUs like the EPS32 or ESP8266 which don't have direct USB (and use an external USB-to-serial chip) suffer from this problem more than the other devices.

I've always wanted to implement a comms layer which gets uploaded to the remote device once and have rshell communicate with the remote device using that, but that would require some fairly extensive changes,

@ropg
Copy link

ropg commented May 24, 2021

I fixed #27 and some other people's issues (or so I believe), with a -s, '--suppress-reset` command-line option. Not only was it slowing things down, it was also messing with people whose board is in a state where something doesn't cleanly unload and the gc turns the soft-reboot into a hard one, which messes with the send/expect sequences in pyboard.

Pull Request is in, see the issue for all the details.

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

3 participants