Dashboard page has 90+ % CPU utilization

[Rangak]

When on Dashboard page, CPU utilization on router is very high, The bytecount script is responsible for this. Figure out alternative (e.g no python or cython) for this script to bring
CPU utilization down.

[Rangak]

Websockets would be an easy way to solve this. Instead of periodic XHR to fetch bytecount, open a websocket when user goes to Dashboard page. Then send back the bytecounts periodically over the websocket. One can also break up the response in the dashboard python script with this websocket to speed up the dashboard page load time. See also #274 comments. Such websockets implementation needs security review to avoid introduction of vulnerabilities.

[ThePletch]

I can work on this.

[Rangak]

Cool ! Feel free to ping me if I can answer any questions.

[ThePletch]

@Rangak Pretty much done with the client-side part of this, and the server-side part looks fairly simple (maintain a list of connected clients, send them updated bytecounts every n seconds, where n is a value that doesn't cripple the router), but the 'every n seconds' part is the challenge.

Is there a better way to regularly execute some code on lighttpd than just defining a cron job?

[Rangak]

Great ! Are you using https://github.com/nori0428/mod_websocket ? You could just modify the bytecount python script to wake up 'every n seconds' and send to mod_websocket. That would be the simplest thing to do, rather than start a cron job. There needs to be a way to stop the bytecount script when the user goes away from the dashboard page. Not sure how that would work.

[ThePletch]

I'm actually fairly unfamiliar with Lighttpd and am stuck on where/how to install mod_websocket.

Conceptually, this seems as simple as "run the bytecount script every n seconds, exit if there are no clients," just using mod_websocket's default 20-second ping to ensure that inactive clients/users not still on the page are disconnected. Given a typical router, I don't think that sending a few bytecount updates that aren't received will cause many issues.

[Rangak]

Were you able to progress with mod_websocket ? If not how are you testing the client side work you completed ? There are other lighttpd modules in use; looking at that will
tell you how to install mod_websocket.

Regarding the exiting of bytecount script, your solution using mod_websocket's 20 second ping should be adequate.

[Rangak]

Can I help ?

[Rangak]

Hi, I am motivated to make progress on this and can help complete it. Perhaps we could discuss how to land this. Thanks.