383 bytes
20042 so far
30 bytes
20425 so far
383 bytes
20455 so far
30 bytes
20838 so far
383 bytes
20868 so far
31 bytes
21251 so far
383 bytes
21282 so far
31 bytes
21665 so far
383 bytes
21696 so far
31 bytes
22079 so far
383 bytes
22110 so far
271 bytes
22493 so far
9 bytes
22764 so far
4 bytes
22773 so far
(mine crashes around here)
yours happily cruises along:
74 bytes
25212 so far
74 bytes
25286 so far
60 bytes
25360 so far
115 bytes
25420 so far
77 bytes
25535 so far
75 bytes
25612 so far
74 bytes
25687 so far
74 bytes
25761 so far
74 bytes
25835 so far
74 bytes
25909 so far
74 bytes
25983 so far
74 bytes
26057 so far
74 bytes
26131 so far
So the question becomes, why does my code fetch larger chunks? I don't think I've configured anything to specifically ask for larger chunks...
I've just added the flow control code to your example and I still get 69byte chunks, so its not the flow control.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Oh now this is interesting.
Here's what I get when I use your code with all the rest of my stuff deleted:
(fairly consistent 69byte chunks).
With my code:
(fairly consistent 300+ byte chunks).
If I add some extra logging:
(mine crashes around here)
yours happily cruises along:
So the question becomes, why does my code fetch larger chunks? I don't think I've configured anything to specifically ask for larger chunks...
I've just added the flow control code to your example and I still get 69byte chunks, so its not the flow control.