CPU utilization?

[Dolf Starreveld]

Is there a way to find out, possibly even over time, what the CPU utilization is/was? That will give me some insight as to how much "room" I have for additional cameras, or what the effect of tuning camera settings is.

[Arno Hautala]

Even better, if this information was available per-camera. I have two different models of cameras and it'd be nice to evaluate if one is less demanding than the others.

[CamectChao]

We don't officially support it. But if you really want to know it, it's on the local HTTP server: https://xxxx.home.camect.com/debug/prof/  (You can find the full home name by accessing https://local.home.camect.com/)

Please note: this was designed for our own debug purpose only. We don't promise anything to users for this feature.

[AAron nAAs]

I tried hitting https://local.home.camect.com/ with Fiddler while decrypting.

For /list.json, the response body looks like (redacted):

[{"url":"https://12345abcd.l.home.camect.com:443/","name":"MyHome"}]

Are you referring to this?

https://12345abcd.l.home.camect.com:443/debug/prof

(This host resolves, though it seems to be listening and not replying)

I also tried:

https://MyHome.home.camect.com:443/debug/prof

(This host doesn't resolve, so must be wrong)

I'm a dev guy. You've got me curious.

Thanks and I understand the big disclaimer.

[Arno Hautala]

OK, this is neat. I got it to work by hitting the IP (local domain name works too) of my Camect and ignoring the invalid SSL cert warning (feature request: API to supply our own SSL cert to be used when accessing via the local domain).

It looks like this is a process list and statistical counts (count, average, std. dev., min, max). You can filter by process name and there are processes for each camera, labeled with the IP. There are also labels for motion and object detection, disc access, memory. You can click on a label to get a chart of the last hour.

I can't see spending much time here, but for debugging it's nice to know it's available. I'll definitely take a look at this whenever I change my camera numbers.

Thanks for pointing it out, Chao!

[Arno Hautala]

Weird, my xxxx.l.home.camect.com address wasn't resolving so I used the IP and local domain. Now the xxxx address is working. Must have been a brief DNS glitch.

[AAron nAAs]

Ok, I got those to work.

(I think Camect doesn't like my subnets, but I added that question to another thread.)

On the same subnet, I can access those links.

I added a local user/password with admin access for the login.

Cool & interesting profiling information.

Be sure to share more cool tips like this in the future!

Thanks