Browser hangs and takes too long to render the topology on openshift (using skydive operator)

[rayalaka]

I have deployed skydive operator on openshift and I am facing below problems. Please help me in resolving the issues.

1. The ui is taking too long time to load the topology and frequently browser says 'Page unresponsive' (using Google chrome and firefox).
2. Frequently I see connected/disconnected messages on the right hand top corner.
3. The agent running on the node where analyzer is running is connected to the analyzer and rest of the agents (daemon sets are unable to connect to the analyzers and the below is found in logs.

2020-08-23T18:30:51.434Z        INFO    websocket/client.go:492 (*Client).Connect       ip-10-0-143-120: Connecting to ws://172.30.75.207:8082/ws/agent
2020-08-23T18:33:02.506Z        INFO    websocket/client.go:492 (*Client).Connect       ip-10-0-143-120: Connecting to ws://172.30.75.207:8082/ws/agent
2020-08-23T18:35:13.578Z        INFO    websocket/client.go:492 (*Client).Connect       ip-10-0-143-120: Connecting to ws://172.30.75.207:8082/ws/agent
2020-08-23T18:37:24.650Z        INFO    websocket/client.go:492 (*Client).Connect       ip-10-0-143-120: Connecting to ws://172.30.75.207:8082/ws/agent
2020-08-23T18:39:35.722Z        INFO    websocket/client.go:492 (*Client).Connect       ip-10-0-143-120: Connecting to ws://172.30.75.207:8082/ws/agent
2020-08-23T18:41:46.794Z        INFO    websocket/client.go:492 (*Client).Connect       ip-10-0-143-120: Connecting to ws://172.30.75.207:8082/ws/agent
2020-08-23T18:43:57.866Z        INFO    websocket/client.go:492 (*Client).Connect       ip-10-0-143-120: Connecting to ws://172.30.75.207:8082/ws/agent

[schmurfy]

This is frustrating because this project almost does what I need but I can't make any use of it, I tried using the skydrive-helm, after the install I can open the web ui, setup a capture, view a few packets and then... the ui hangs, the chrome tabs starting using ~97% cpu and from that point the ui is unusable. I tried another browser, killed and restarted the chrome tab but all my tests ending up the same way: the tab takes a log of cpu and does not even manage to display anything.

That's very disappointing :/

Ps: That's not even on a big cluster, it was only on a three node clusters with less than 10 pods of each

[safchain]

Hello, sorry for the late reply. What kind of capture did you start, only one interface ? multiple interfaces ?

• Maybe you could try the other/future version of the WebUI: https://github.com/skydive-project/skydive-ui
• Or you could specify a default filter so that the WebUI will be less crowded https://github.com/skydive-project/skydive/blob/master/etc/skydive.yml.default#L531-L541