Success! At least I know I was on the right trail...
I rebuilt Espruino for my Pico with a socketserver send buffer and chunkSize of 2048 bytes instead of 64. Now my copy of the Espruino Reference HTML file takes about 3 minutes to load from the SD card and appear via the ESP8266 over wifi in the browser. Previously it took around 25 minutes for exactly the same file! ;))
I know I've sacrificed some precious Pico RAM 'just' for a transmit buffer, but the experiment was worth it to learn how to rebuild and very slightly modify Espruino for myself.
I'm just wondering if it's worth adding some optional parameters to the socket functions to point to user-defined buffers (and define their size) so that instead of using the small pre-defined buffer you could, depending on RAM constraints, the hardware modules and the application, define your own buffers.
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.
Success! At least I know I was on the right trail...
I rebuilt Espruino for my Pico with a socketserver send buffer and chunkSize of 2048 bytes instead of 64. Now my copy of the Espruino Reference HTML file takes about 3 minutes to load from the SD card and appear via the ESP8266 over wifi in the browser. Previously it took around 25 minutes for exactly the same file! ;))
I know I've sacrificed some precious Pico RAM 'just' for a transmit buffer, but the experiment was worth it to learn how to rebuild and very slightly modify Espruino for myself.
I'm just wondering if it's worth adding some optional parameters to the socket functions to point to user-defined buffers (and define their size) so that instead of using the small pre-defined buffer you could, depending on RAM constraints, the hardware modules and the application, define your own buffers.