How much UDP and TCP traffic does Evothings generate

[rhabyt]

I'm an American professor teaching a class in the internet of things in Croatia. We have four copies of Evo Workbench and four (at least) copies of Evo Client (all on a mix of Mac, Windows, iOS, and Android) running on the same antiquated domestic wifi router. Everything is constantly crashing and I am trying to find out if it is just all the Evothings traffic causing the router to crash, or some other sequence of events. So my question is, how much traffic (and crosstalk) would four Workbenches and four Clients generate? Would that be enough to bring down a 14-year old Apple Airport Base Station, or should I be looking elsewhere?

[micke]

Dear Sir,

It might be the router, however, I am not up-to-date regarding the evolution of router performance. Perhaps the difference is huge between old and modern routers.

What you could test is to see how the performance is with one Workbench and one mobile device (client app). Then add another mobile device, and so on. To gradually increase network load and see where the limit is.

The amount of UDP traffic should be zero once connected. I would say that socket.io accounts for the most frequent TCP traffic (Evothings Studio uses socket.io to stablish a live connection between the client app and the workbench).

Hope this helps!

Very best regards, Mikael

[micke]

Just a question, is it when connecting the crashes occur, or on RUN/Reload?

If connecting works, then the socket.io traffic is likely not the problem. If RUN/Reload does not work, it is likely the transfer of the files that brings the router down.

The Evothings examples are a bit heavyweight in that they contain custom font files. What you can try is a plain index.html file that does not load any external CSS/fonts, and see if that works better (less data to transfer).

Very best, Mikael