# Troubleshooting

## Q: Why is the performance on CPU sometimes better than on GPU, when running pipeline benchmarking like stream density?

A: The performance of pipeline benchmarking strongly depends on the models. For `yolo11n` object detection specifically, it is recommended to use the model precision FP32 when it is running on a `GPU` device. If supported, you can then change the model precision by updating the pipeline script to point to the precision of your choice. For example, you can change the model from `FP16` to `FP32`, assuming the precision `FP32` of the target model is available:

```bash
    src/pipelines/yolo11n.sh

    ...
    model=models/object_detection/yolo11n/FP16/yolo11n.xml
    ...
```

## Q: What happens if the system keeps crashing when building the `dlstreamer-realsense` image?

A: Some systems may run into memory issues when building the `dlstreamer-realsense` image. In the `Dockerfile.dlstreamer` file, change the make command to not use the `-j` threading option.

```diff
- make -j"$(cat < /proc/cpuinfo |grep -c proc)" &&
+ make &&
```

## Q: What happens if the RTSP source is not found?

A: Depending on your system's performance it is possible that the RTSP simulator may take additional time to initialize and start streaming. To avoid issues you can add a waiting period before the pipeline starts. For example, you can add a 5 second sleep timer to /src/entrypoint.sh.

```bash
sleep 5 # sleep for 5 seconds before starting the pipeline
eval $gstLaunchCmd
```

## Q: How can I use an Intel RealSense Camera as the input?

A: To use a RealSense camera as an input for any of the retail use cases, you need to obtain the serial number first. Follow the instructions in the [RealSense repository](https://github.com/realsenseai/librealsense/tree/master/tools/enumerate-devices) to run `rs-enumerate-devices` and obtain the following information:

```
Device Name                   Serial Number       Firmware Version
Intel RealSense D415          725112060400        05.12.02.100
Device info:
    Name                          :     Intel RealSense D415
    Serial Number                 :     725112060400
    Firmware Version              :     05.12.02.100
    Recommended Firmware Version  :     05.12.02.100
    Physical Port                 :     \\?\usb#vid_8086&pid_0ad3&mi_00#6&2a371216&0&0000#{e5323777-f976-4f5b-9b55-b94699c46e44}\global
    Debug Op Code                 :     15
    Advanced Mode                 :     YES
    Product Id                    :     0AD3
    Camera Locked                 :     NO
    Usb Type Descriptor           :     3.2
    Product Line                  :     D400
    Asic Serial Number            :     012345678901
    Firmware Update Id            :     012345678901
```

Simply add the serial number to the `INPUTSRC` argument when calling the pipelines:

```
INPUTSRC=725112060400 make run-demo
```

## Q: How to configure the centralized proxy?

A: Please follow the below steps to configure the proxy

### 1. Configure Proxy for the Current Shell Session

```bash
export http_proxy=http://<proxy-host>:<port>
export https_proxy=http://<proxy-host>:<port>
export HTTP_PROXY=http://<proxy-host>:<port>
export HTTPS_PROXY=http://<proxy-host>:<port>
export NO_PROXY=localhost,127.0.0.1,::1
export no_proxy=localhost,127.0.0.1,::1
export socks_proxy=http://<proxy-host>:<port>
export SOCKS_PROXY=http://<proxy-host>:<port>
```

### 2. System-Wide Proxy Configuration

System-wide environment (/etc/environment)
(Run: sudo nano /etc/environment and add or update)

```bash
http_proxy=http://<proxy-host>:<port>
https_proxy=http://<proxy-host>:<port>
ftp_proxy=http://<proxy-host>:<port>
socks_proxy=http://<proxy-host>:<port>
no_proxy=localhost,127.0.0.1,::1

HTTP_PROXY=http://<proxy-host>:<port>
HTTPS_PROXY=http://<proxy-host>:<port>
FTP_PROXY=http://<proxy-host>:<port>
SOCKS_PROXY=http://<proxy-host>:<port>
NO_PROXY=localhost,127.0.0.1,::1
```

### 3. Docker Daemon & Client Proxy Configuration

Docker daemon drop-in (/etc/systemd/system/docker.service.d/http-proxy.conf)
Create dir if missing:
sudo mkdir -p /etc/systemd/system/docker.service.d
sudo nano /etc/systemd/system/docker.service.d/http-proxy.conf

```bash
[Service]
Environment="http_proxy=http://<proxy-host>:<port>"
Environment="https_proxy=http://<proxy-host>:<port>"
Environment="no_proxy=localhost,127.0.0.1,::1"
Environment="HTTP_PROXY=http://<proxy-host>:<port>"
Environment="HTTPS_PROXY=http://<proxy-host>:<port>"
Environment="NO_PROXY=localhost,127.0.0.1,::1"
Environment="socks_proxy=http://<proxy-host>:<port>"
Environment="SOCKS_PROXY=http://<proxy-host>:<port>"

# Reload & restart:
sudo systemctl daemon-reload
sudo systemctl restart docker

#  Docker client config (~/.docker/config.json)
#  mkdir -p ~/.docker
#  nano ~/.docker/config.json
{
  "proxies": {
    "default": {
      "httpProxy": "http://<proxy-host>:<port>",
      "httpsProxy": "http://<proxy-host>:<port>",
      "noProxy": "localhost,127.0.0.1,::1"
    }
  }
}
```