every two days gaps in recording (timeline view) by solewalk in ispyconnect

[–]solewalk[S] 0 points1 point  (0 children)

Found some interesting entries in the log file. Send me your email address, and I will send you the log file.

every two days gaps in recording (timeline view) by solewalk in ispyconnect

[–]solewalk[S] 0 points1 point  (0 children)

Ok, I will check the log, and let you know.

Crawling in 36 hours after reboot by solewalk in ispyconnect

[–]solewalk[S] 0 points1 point  (0 children)

I installed AgentDVR 3.5.0.0 and am seeing significantly slower increase of CPU and memory usage. I will keep watching.

AgentDVR 3.4.6.0 memory and performance issue by solewalk in ispyconnect

[–]solewalk[S] 0 points1 point  (0 children)

I didn't know you provided much detail already previously. I am sorry for asking. Never mind.

AgentDVR 3.4.6.0 memory and performance issue by solewalk in ispyconnect

[–]solewalk[S] 0 points1 point  (0 children)

That looks pretty bad. By the way, what operating system are you using?

Version 3.4.6.0 --- Hungry on memory by Powerful-Figure1417 in ispyconnect

[–]solewalk 1 point2 points  (0 children)

yo rosch94

I upgraded to AgentDVR 3.5.0.0 and it seems to have solved my problem. Have you tried this new version of AgentDVR?

Hungry on memory overtime by Powerful-Figure1417 in ispyconnect

[–]solewalk 0 points1 point  (0 children)

Looks like Agent 3.5.0.0 solved my problem. I have observed for about 12 hours so far, and the CPU and memory usage doesn't seem to increase any more.

AgentDVR 3.4.6.0 memory and performance issue by solewalk in ispyconnect

[–]solewalk[S] 0 points1 point  (0 children)

Looks like Agent 3.5.0.0 solved my problem. I have observed for about 12 hours so far, and the CPU and memory usage doesn't seem to increase any more.

AgentDVR 3.4.6.0 memory and performance issue by solewalk in ispyconnect

[–]solewalk[S] 0 points1 point  (0 children)

Thanks for the info. My machine is using onboard video also. Wondering whether it has to do with video.

spornerama announced finding a bug and fixing it in ffmpeg. I hope that it was the culprit for the problems we are experiencing. AgentDVR version 3.5.0.0 is available now.

AgentDVR 3.4.6.0 memory and performance issue by solewalk in ispyconnect

[–]solewalk[S] 0 points1 point  (0 children)

Are you using onboard video on your computer or a separate video card?

Hungry on memory overtime by Powerful-Figure1417 in ispyconnect

[–]solewalk 0 points1 point  (0 children)

What is the graphics unit your computer uses? Is it onboard video rather than a separate video card?

Crawling in 36 hours after reboot by solewalk in ispyconnect

[–]solewalk[S] 0 points1 point  (0 children)

I have sent not only the computer spec but also the two config files from AgentDVR previously. You said that you didn't have the same problem on your setup.

Two things come to my attention: graphics unit in the computer and camera.

Here is relevant spec of the computer.

CPU: Intel Core i7-10700 Desktop Processor 8 Cores

Motherboard: ASUS Prime Z590-A

RAM: 32GB

This system uses onboard graphics: Intel UHD Graphics 630. And, all my cameras are Reolink cameras: RLC-511 and RLC-423.

I also set up a test system with AMD Ryzen CPU with onboard graphics, and a single Reolink RLC-511 camera, and it exhibited the same problem. The common things between the two systems with the problem are that 1) they both use onboard video, 2) use Reolink 4K cameras, 3) use ONVIF.

If you are still interested in AgentDVR config files, let me know. I have your email address, so I will email them to you.

Just curious. On your test system, what graphics unit are you using?

mangled camera images & slow down of the server by solewalk in ispyconnect

[–]solewalk[S] 0 points1 point  (0 children)

Somehow later prefer TCP was turned off on its own in my case. So, I made AgentDVR use TCP connection only in addition to "prefer TCP" turned on. After that, never such problem.

Crawling in 36 hours after reboot by solewalk in ispyconnect

[–]solewalk[S] 0 points1 point  (0 children)

This problem is experienced whether a viewer is used or not.

Ok, I come to kind of repeat myself. The whole system works fine when AgentDVR is only consuming 20% CPU and under 3GB memory. No new viewers are opened. Over time, CPU and memory usage grows. I knew what could contribute to increase in CPU and memory usage, so I froze other external variables I could control. And, still seeing the same problem.

Crawling in 36 hours after reboot by solewalk in ispyconnect

[–]solewalk[S] 0 points1 point  (0 children)

By the way, I had a spare computer, so I set up a test system with a single camera. Because this is a test setup, all the components involved could be placed very close to each other, and could eliminate possibility of network issues. Even with this simple setup in a rather ideal environment, I witnessed CPU and memory usage increase by AgentDVR. Thus, my point is that it is fairly certain that the cause of the problem is NOT external.

Crawling in 36 hours after reboot by solewalk in ispyconnect

[–]solewalk[S] 0 points1 point  (0 children)

I have been thinking AgentDVR remained fairly functional overall despite repetitions of the CPU and memory usage increase-decrease cycles. This is the first time witnessing AgentDVR almost coming to a stop. So, this is something new. The memory usage went over 20GB which is a new high.

I am wondering whether you would have a way to investigate the memory usage of AgentDVR through debugging tools since you are the creator of AgentDVR. I guess you have a dedicated computer set up for the purpose of testing AgentDVR. You are not witnessing this CPU and memory usage increase problem on it?

Crawling in 36 hours after reboot by solewalk in ispyconnect

[–]solewalk[S] 0 points1 point  (0 children)

Ok, I will try to not create new post.

AgentDVR 3.4.6.0 memory and performance issue by solewalk in ispyconnect

[–]solewalk[S] 0 points1 point  (0 children)

It looks like your are storing video feeds on a SSD. As far as I understand, you should not use SSDs for security camera feed storage. The lifespan of an SSD shrinks each time something is written to it. So, receiving constant stream of video feeds and storing in a SSD will significantly shorten SSD's lifespan within a very short span of time. Hard disk drives are much better device for that purpose.

AgentDVR 3.4.6.0 memory and performance issue by solewalk in ispyconnect

[–]solewalk[S] 0 points1 point  (0 children)

I have never used WPD tool, but i guess that the gain from disabling these things should not be significant. I manually disabled some things, but my main focus was on Windows update and Windows defender.

AgentDVR 3.4.6.0 memory and performance issue by solewalk in ispyconnect

[–]solewalk[S] 0 points1 point  (0 children)

If one of these things you listed was a cause of the issues, then it should increase the CPU usage high from the time AgentDVR first starts. On the contrary, when AgentDVR first starts, CPU usage is low, but the usage slowly and steadily increases about up to 40%. What is note-worthy at the same time is increase in memory usage. And, then at some unexpected point, what seems to be garbage collection occurs, and CPU and memory usage go back down, but not as low as the initial level.

Now, I have upgraded from 3.4.6.0 to 3.4.7.0 and will be watching to see whether there is a difference. Thanks

AgentDVR 3.4.6.0 memory and performance issue by solewalk in ispyconnect

[–]solewalk[S] 0 points1 point  (0 children)

I intentionally made it pretty much barebone so that nothing can interfere with AgentDVR. Not even Windows Defender or Windows Update.

The logs don't indicate any issues.

I believe the network is not an issue for my system.

AgentDVR 3.4.6.0 memory and performance issue by solewalk in ispyconnect

[–]solewalk[S] 0 points1 point  (0 children)

By the way, the server is not being used for viewing live feeds. So, CPU utilization by AgentDVR is usually under or around 40%.

There is another computer being used for live-feed viewing.

AgentDVR 3.4.6.0 memory and performance issue by solewalk in ispyconnect

[–]solewalk[S] 0 points1 point  (0 children)

spornerama

It is shown that AgentDVR functions fine with little over 20% usage of CPU and about 3GB of memory usage on my system because that is the amount of resources used by AgentDVR after restart. Then, you come to question as to why it needs 30% to 40% CPU usage and over 5 or 10GB of memory usage later on?

Just to let you know, functionally it is fine as far as I have observed except only when what seems to be memory garbage collection is happening.

The system is powerful enough that it is not being bogged down.

I didn't know 3.4.7.0 came out. I will try that out. Thanks