Hi , i face some issues where when i turn on the dev mode and try to access the nodered editor , the network on my gateway (located on remote location) becomes so slow , in fact when i try to ping the device the response time took so long
PS C:\Users\annas_tanalink\Desktop> ping x.x.x.x
Pinging x.x.x.x with 32 bytes of data:
Reply from x.x.x.x: bytes=32 time=3849ms TTL=49
Request timed out.
Reply from x.x.x.x: bytes=32 time=3692ms TTL=49
Reply from x.x.x.x: bytes=32 time=2755ms TTL=49
and this is the result when i try to access the editor
But on my other gateways it is okay , please do note that im using different hardware for both gateway where the gateway that has problem is running on rpi4b but the other good no problem gateway is running on cm4 , any thoughts on this issue ? have this issue been faced before ? Thanks
I think we need to know a little bit more about your network setup here. How are your gateways connecting back? Is it using a VPN?
Just enabling the editor access should not cause a large increase in network or CPU usage, but actually accessing the editor will cause all requests to the editor flow over a websocket tunnel.
It would be useful to see the load on the device at the time.
btw this is the time when the gateway became slow , i believe this is the time the gateway become slow because I dont see any resources data being published to my cloud influxdb
OK, that’s not pointing to anything immediately obvious at the moment.
Can you describe the network connection for the 2 instances, if it’s not a VPN is it a cellular link of some sort? If so what sort of upstream bandwidth do you normally get from the device?
but now i still have the credit since i just purchased it
“The editor can be slow to load first time, how long did you leave it? 1mbps upload is pretty slow these days.”
The editor i leave it until it completed the loading , I suspect this issue might be because of network speed I guess , but I need to cross check and compare the network speed with my other good no problem gateway first ,
btw I think the better questions is what are the bare minimum network speed that is needed to access the nodered editor through flowfuse dev mode ? Because previously I run the nodered natively and expose it to public IP and it works quite well , no issues of slowing down significantly as compared to how i run using flowfuse , any thoughts ?
Just an update , I believe this is due to network connection speed since on my
DEV Gateway
Retrieving speedtest.net server list...
Selecting best server based on ping...
Hosted by Maxis (Kuala Lumpur) [0.98 km]: 15.104 ms
Testing download speed................................................................................
Download: 42.40 Mbit/s
Testing upload speed......................................................................................................
Upload: 26.02 Mbit/s
I can access the dev gatway quite easily , no big issues
Prod Gateway 1
Retrieving speedtest.net server list...
Selecting best server based on ping...
Hosted by Celcom Axiata (Kuala Lumpur) [1626.27 km]: 33.063 ms
Testing download speed................................................................................
Download: 3.92 Mbit/s
Testing upload speed......................................................................................................
Upload: 1.32 Mbit/s
This the network connection speed for the prod gateway that Im not able to access the editor
Prod Gateway 2
Retrieving speedtest.net server list...
Selecting best server based on ping...
Hosted by GB Network Solutions Sdn Bhd (Cyberjaya) [4.70 km]: 57.708 ms
Testing download speed................................................................................
Download: 2.95 Mbit/s
Testing upload speed......................................................................................................
Upload: 1.52 Mbit/s
This the network connection speed for the prod gateway that Im able to access the editor from but only with google chrome , If i try to access the editor using incognito mode , im not able to do so for both prod gateway , only the dev gateway is accessible if using incognito mode , I believe this is related with the google chrome cache features ? thats why im able to access it thru normal google chrome but not incognito mode
Reply from 183.171.153.189: bytes=32 time=31ms TTL=49
Reply from 183.171.153.189: bytes=32 time=33ms TTL=49
Reply from 183.171.153.189: bytes=32 time=36ms TTL=49
Reply from 183.171.153.189: bytes=32 time=32ms TTL=49
Reply from 183.171.153.189: bytes=32 time=31ms TTL=49
Reply from 183.171.153.189: bytes=32 time=33ms TTL=49
Reply from 183.171.153.189: bytes=32 time=31ms TTL=49
Reply from 183.171.153.189: bytes=32 time=30ms TTL=49
Reply from 183.171.153.189: bytes=32 time=31ms TTL=49
Reply from 183.171.153.189: bytes=32 time=32ms TTL=49
Reply from 183.171.153.189: bytes=32 time=33ms TTL=49
Reply from 183.171.153.189: bytes=32 time=36ms TTL=49
Reply from 183.171.153.189: bytes=32 time=40ms TTL=49
Reply from 183.171.153.189: bytes=32 time=41ms TTL=49
Reply from 183.171.153.189: bytes=32 time=31ms TTL=49
Reply from 183.171.153.189: bytes=32 time=32ms TTL=49
Reply from 183.171.153.189: bytes=32 time=32ms TTL=49
Reply from 183.171.153.189: bytes=32 time=488ms TTL=49
Reply from 183.171.153.189: bytes=32 time=385ms TTL=49
Reply from 183.171.153.189: bytes=32 time=553ms TTL=49
Reply from 183.171.153.189: bytes=32 time=524ms TTL=49
Reply from 183.171.153.189: bytes=32 time=453ms TTL=49
Reply from 183.171.153.189: bytes=32 time=788ms TTL=49
Reply from 183.171.153.189: bytes=32 time=750ms TTL=49
Reply from 183.171.153.189: bytes=32 time=1545ms TTL=49
Reply from 183.171.153.189: bytes=32 time=2797ms TTL=49
Reply from 183.171.153.189: bytes=32 time=3413ms TTL=49
Reply from 183.171.153.189: bytes=32 time=3090ms TTL=49
Reply from 183.171.153.189: bytes=32 time=3396ms TTL=49
Reply from 183.171.153.189: bytes=32 time=3603ms TTL=49
Reply from 183.171.153.189: bytes=32 time=2746ms TTL=49
Reply from 183.171.153.189: bytes=32 time=3291ms TTL=49
Reply from 183.171.153.189: bytes=32 time=1799ms TTL=49
Reply from 183.171.153.189: bytes=32 time=1957ms TTL=49
Reply from 183.171.153.189: bytes=32 time=2157ms TTL=49
Reply from 183.171.153.189: bytes=32 time=2786ms TTL=49
Reply from 183.171.153.189: bytes=32 time=1540ms TTL=49
Reply from 183.171.153.189: bytes=32 time=1553ms TTL=49
Reply from 183.171.153.189: bytes=32 time=1460ms TTL=49
Reply from 183.171.153.189: bytes=32 time=1497ms TTL=49
Reply from 183.171.153.189: bytes=32 time=1918ms TTL=49
Reply from 183.171.153.189: bytes=32 time=2301ms TTL=49
Reply from 183.171.153.189: bytes=32 time=1995ms TTL=49
Reply from 183.171.153.189: bytes=32 time=2763ms TTL=49
Upon initially pinging the gateway, I observed consistently low response times around 30-40 milliseconds, indicating good network conditions. However, as soon as I attempted to access the Node-RED editor, the response times exhibited a dramatic increase, ranging from 2000 milliseconds to 3000 milliseconds, with some even reaching as high as 3500 milliseconds.
This is going to be because it is saturating the uplink speed. It is important to remember that speed is measured in bits per second not bytes per second, and those speeds are to the closest speed test server, not to AWS Data center in Europe where the FlowFuse app is hosted
The Node-RED editor page is around 4mb, so at an absolute minimum it could take over 30 seconds to upload the data, hence why it does better when the page is cached.
We are working on approaches to improve this, but it is not a simple task
I see , okay then , thank you for the clarification , I guess on the flowfuse side , I just need to wait on the next release right ? are there any suggestions that you can provide to tackle this issue for now , maybe in terms of hardware side or others ? Thanks
I think the only thing that will help at the moment is a faster uplink speed, which I suspect is going to be limited by either the cellular modem or the network operator/tariff.
I now have a test environment where I can limit the uplink speed so we can test some options.
Hi , just to update , I use throttle to simulate slow networks on my development gateways and I faced the same issues which is not able to access the device editor
