Page 1 of 1

Performance Issue

PostPosted: Mon Nov 03, 2014 3:36 pm
by Logistics
Hello,

I'm using Xeoma 14.6.23 and attempting to run twenty cameras off of one server. I'm having an issue where adding more than seven cameras spikes the CPU load on each core to hit anywhere from 95 - 100% usage. Obviously the server becomes unresponsive and the camera feeds start to look distorted or crash all-together.

The server is admittedly far from the best but the performance calculator leads me to believe that it should be capable of what I'm trying to do.
(See attached image below).

The server specs are as follows:

OS: Ubuntu 14.04 LTS (64-bit)
Processor: Intel® Xeon(R) CPU E3-1220 V2 @ 3.10GHz × 4
Graphics: Gallium 0.4 on NVC1
Memory: 4 GiB

So far I've found two working strings for the cameras. One for h264 and the other for a standard definition - I'm not certain if it is actually using mjpeg though.

HD:
rtsp://{IP Address}:554/1/h264major

Standard:
rtsp://{IP Address}:554//0/:/main

Oddly enough these two strings take up roughly the same amount of resources and hit a seven camera limit.

The cameras that are being used claim the model of GT720TPOE but a Google search really doesn't yield a great deal of information. The web interface for the cameras shows TI-LC13 series for the product info. Here's the store page that they were bought from if you're interested.

I was wondering if anybody can point to a solution? I'm really trying to avoid a hardware upgrade since there'll be some real resistance from upper management about spending money.

Thanks.

Re: Performance Issue

PostPosted: Fri Nov 07, 2014 12:12 pm
by Logistics
Response from the Xeoma support team after contacting them directly:

First of all, if your license allows that, we'd recommend you to update to the latest version of Xeoma available - official release Xeoma 14.7.18 or beta version 14.10.24, both available at http://xeoma.com/

Now please try to play these URLs you sent us in the VLC player (Ctrl+N to open the dialog in VLC). While the URL is being played, hit Ctrl+J to see the stream's parameters. Compare those of both URLs. I believe that the resolution is nearly the same for both streams.

Please try these URLs as well

rtsp://{IP Address}:554/cam/realmonitor?channel=0&subtype=1
rtsp://{IP Address}:554/cam/realmonitor?channel=1&subtype=1
rtsp://{IP Address}:554/cam/realmonitor?channel=2&subtype=1

rtsp://{IP Address}:554/cam/realmonitor?channel=0&subtype=0
rtsp://{IP Address}:554/cam/realmonitor?channel=0&subtype=2

rtsp://{IP Address}:554/cam/realmonitor?channel=1&subtype=0
rtsp://{IP Address}:554/cam/realmonitor?channel=1&subtype=2

rtsp://{IP Address}:554/cam/realmonitor?channel=2&subtype=0
rtsp://{IP Address}:554/cam/realmonitor?channel=2&subtype=2

Neither of the URLs you sent looks like MJPEG, so there's a doubt if the camera supports MJPEG at all. If it doesn't, what we can recommend is to use an H264 stream with as low parameters as you can for preview (shown on the Main screen), while archiving in higher quality.

Once we find the URL for the sub stream, you will need to go to the web interface of your camera in a browser and see what settings are there for the main and sub streams. Set the sub stream to lowest acceptable parameters.


The above suggestion worked great and allowed for a great deal more cameras to be added. It seems that any further tweaking will need to be done with the cameras themselves.