Does BI need to be rebooted often? or how to optimize stability? [RDP high CPU usage]

There is something else going on. Why dont you test with an actual monitor to start. I have seen an ethernet driver cause this exact issue. You should be at 5-10 percent or less even with no substreams.
 
  • Like
Reactions: Webfont and sdkid
fenderman said:
There is something else going on. Why dont you test with an actual monitor to start. I have seen an ethernet driver cause this exact issue. You should be at 5-10 percent or less even with no substreams.
Click to expand...

Yes I tested that last night;

Webfont said:
If I login directly it behaves much better;

View attachment 157997
View attachment 157998
Click to expand...

No substreams and BI was sitting at about 10% when the PC was accessed with a normal monitor/keyboard/mouse.

Maybe it's my Windows 10 LTSC. I'll reinstall with a normal pro like it had before and will compare.
 
Since you only have one camera, disable it in BI and your CPU should be at 0%.

If not, then clearly something else is going on in your system. One camera on a 7th gen should not be running that high CPU.
 
OK since it is only one camera, delete it from BI, then add it again. Sometimes a camera goes wonky in BI.

Add camera
Type in IP address, username, and password
Hit the Find/inspect key
Post a screenshot of the pop up window that appears with Find/inspect.

Then try again and see if the CPU drops.
 
Opening 192.168.1.108 port 80...
HTTP Get / request...
OK
ONVIF GetSystemDateAndTime
2023-03-26T16:14:20.000Z
Requesting device information...
Manufacturer: Dahua
Model: SD49225XA-HNR
FirmwareVersion: 2.800.1341000.0.R, Build Date 2020-03-12
GetCapabilities...
Querying services
Has Search services: /onvif/search_service
Has Imaging services: /onvif/imaging_service
Has media services: /onvif/media_service
Has RTP_RTSP_TCP, requesting profiles
profile token MediaProfile000
profile name MediaProfile_Channel1_MainStream
profile source is 000
profile source config is 000
profile token MediaProfile001
profile name MediaProfile_Channel1_SubStream1
profile source is 000
profile source config is 000
profile token MediaProfile002
profile name MediaProfile_Channel1_SubStream2
profile source is 000
profile source config is 000
requesting URI for profile MediaProfile000
RTSP URI: /cam/realmonitor?channel=1&subtype=0&unicast=true&proto=Onvif
requesting URI for profile MediaProfile001
RTSP URI: /cam/realmonitor?channel=1&subtype=1&unicast=true&proto=Onvif
requesting URI for profile MediaProfile002
RTSP URI: /cam/realmonitor?channel=1&subtype=2&unicast=true&proto=Onvif
Has Event services: /onvif/event_service
Has WSPullPointSupport
RelayOutputs: 1
RelayOutput: 000/Bistable/open
InputConnectors: 2
Has Device IO services: /onvif/deviceIO_service
AudioOutputs: 1
Has PTZ service: /onvif/ptz_service
Preset: 1=Driveway Wide
Done
Click to expand...
1679847336543.png

Changed from 10fps to 15fps, and unchecked 'display overlays live'

1679847378275.png

And I'm back to my original CPU usage with RDP being the main hog.

1679847459026.png

If I hide the whole live preview with that stats window, RDP seems much happier as it doesn't have to redraw the moving parts :/

1679847680223.png

And just for fun, I've disabled the camera in BI, and opened the camera's web interface instead. Getting the same RDP overhead problem here as well, so it's definitely not a BI issue.

1679848119947.png
 
Yeah my RDP is less than 2%, so something is up in your system.

It could be an ethernet driver issue as Fenderman mentioned above.
 
  • Like
Reactions: Webfont
I think you are getting great advice to investigate the network card or driver. You started this thread asking about restarts.... Do those performance numbers improve on a freshly booted BI computer?

BI is rock-solid, but I don't necessarily trust other components in Windows or the possible impacts of other things I do with the BI computer (not totally 100% devoted to BI), so I do have it set via task scheduler to reboot every day at a given time. That reboot only leaves about a 90 second gap in recording and access each day. My BI computer (a 4th gen I5 Dell put in service in June of 2015) has been running for almost 8 years like this with exceptional reliability across it's life.
 
Freshly rebooted has the same RDP overhead performance issues.
As for the original topic in this thread, I haven't experienced a total BI lockup since the first time it happened on the original W3530 PC; it happened on the second day of having BI installed on that one.
On the new i5-7500 PC I'm on the second day now with no BI issues so far, so at least that's an improvement :)
Both PCs had a fresh install of Win10 LTSC and dedicated to BI.
 
  • Like
Reactions: sdkid
I wonder if LTSC is the issue? Maybe some compatibility issues with that and RDP versus Win10 Pro?
 
It might be - when I tried to install the intel igpu drivers from the 15.45 branch as recommended here, it told me that I had an unsupported OS, so I ended up having to install the latest 31.0.101.2115.
Might have some other weirdness with other drivers, so I'll reinstall with a normal consumer pro later tonight.
 
wittaj said:
Yeah my RDP is less than 2%, so something is up in your system.
Click to expand...
Might be a silly question, but do you have any of those settings in your BI for your RDP to only use 2%?

1679854255861.png

If I activate that first one "video during RDP" to 5-sec updates, then my RDP cpu usage is like yours;

1679855167176.png

Could this be why we're getting different RDP behaviors? I always had that 'unrestricted' "video during RDP" setting.
 
Last edited:
My viewing setting is unrestricted and FPS is set to 15 since I don't run my cams faster than that.
 
You must log in or register to reply here.
Top Bottom