Enable UMM_POISON in debug mode only

[luc-github]

Hi I have a project that work very well on 2.0.0 core - web server is responsive in AP and STA.
When I moved to 2.1.0 display become very slow on STA and so slow in AP that nothing is displaying. my home page ('/') do around 10Ko, I build by part of 1.2K and send part , then build next part and send it to avoid to consume memory and go out of memory - this working very well on 2.0.0.

I saw webserver has been rewritten for 2.1.0- is there any new parameter or setting to fine tune to get same speed as 2.0.0 that I have missed ?

Thanks

[mkeyno]

hi @luc-github , why don't you use the @Links2004 websocket with single connection, or even the ajax, I presume you did that before you declare, you using the TCP/IP only

[luc-github]

Because I need a web server to display web pages, this is not same usage as websocket

[luc-github]

I should add it is not related to #1661
as I do a WiFi.Disconnect() when I am in AP mode
And display is very slow also on STA mode compare to 2.0.0 for same code and same device

[luc-github]

I have tried git version today and same result : very slow - seems 2.1.0 send data but very slowly on my project (https://github.com/luc-github/ESP8266) with my nodemcu 1.0 - when it is fine on 2.0.0

Any idea what changes between 2.0.0 vs 2.1.0 could cause this ?
Also no one experienced same issue on 10k+ pages ?

I have willing to troubleshoot more but no crash, so I do not know what part of code to check
issue happen on big pages but not on small ones - I guess it may be some new timeout but I did not found it yet - so I am stuck on 2.0.0

[mkeyno]

I wonder why every new release miss some feature or previous, I hope @igrr and @Links2004 could finally release the last stable version before the new chip like ESP32 come to market

[TheAustrian]

If you want a static version of the library why not just use the old 2.0.0 that has what you want and worked for your needs?

[luc-github]

@mkeyno this is normal to have some misses and errors - this is a big project and it managed by people on they free time - so full testing is not always possible - regression test can take ages if you do not have enough people to do it - @igrr and others great contributors do a tremendous job, they have to handle issues and new requests permanently - try and you will see.

A way to contribute before asking new feature is to help to check if current ones are ok, giving as much information as possible to reproduce issue, always try to narrow down issue in code to save time to developers - if I can fix by myself, I do and do a PR (unfortunately I did not do a lot....)

[igrr]

@luc-github could you please share the piece of code which constructs and sends the page?
I looked through the change log and see a couple of changes which might cause this, but not sure yet.

[luc-github]

@igrr
yes it is here : https://github.com/luc-github/ESP8266/blob/master/esp8266/webinterface.cpp#L339-L534
I do a dry run to calculate page size to build the header, then rebuild/send parts

Thanks for looking into

[igrr]

Could that be SPIFFS related slowdown? We have updated to a new version of SPIFFS. Is there a way to rule out that possibility?

[luc-github]

OK I will check by building fake 10K page without using SPIFFS , should be easy to do
I keep you posted - thanks