NetSight CPU Utilization very high when editing maps
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-06-2017 09:47 AM
NetSight 7.0.6.27 got a constant cpu load by 50-70% per core when editing maps.
It doesn't matter, if it's a wifi-map or a normal device-map.
That can't be normal, you need to wait 3-4 minutes, before you can can use the NetSight again.
Does anyone has an idea what to do?
It doesn't matter, if it's a wifi-map or a normal device-map.
That can't be normal, you need to wait 3-4 minutes, before you can can use the NetSight again.
Does anyone has an idea what to do?
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-21-2017 06:11 PM
Hello Chacko, do you still need assistance with this issue?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-21-2017 06:11 PM
Our service partner opened a ticket at Extreme, so there should be an answer soon.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-06-2017 12:20 PM
Please specify if the high CPU is on client or on server.
AFAIK it is not expected behaviour.
AFAIK it is not expected behaviour.
Regards
Zdeněk Pala
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎02-06-2017 12:20 PM
I'm connected to the NetSight server via ssh.
With top and "1" (to see each cpu-core) I can see, that each core got a utilization from 60-70% after editing a map. After a few minutes everything is fine and NetSight is usable again. Until that, the whole NetSight (even the Java-Consoles) are too slow to work with them
With top and "1" (to see each cpu-core) I can see, that each core got a utilization from 60-70% after editing a map. After a few minutes everything is fine and NetSight is usable again. Until that, the whole NetSight (even the Java-Consoles) are too slow to work with them
