I use tensorRT code for reasoning yolov3_tiny, the single reasoning time can be up to 0.03s, the pure reasoning is close to 25fps, but why does the _process_yolo_output in data_processing.py need 0.3s once?
How do I accelerate? My input image size is only 416.
I have one more question, that is, I feel the GPU usage of jetson nano is not stable. I open tegrastats to check, “EMC_FREQ 0% GR3D_FREQ 99%”, sometimes 99%, sometimes 13%, sometimes 0%, is this normal?
When I run my yolov3_tiny, my memory is full, too
I rewrote these 2 functions in NVIDIA’s orginal yolov3_onnx sample.
def sigmoid(value):
"""Return the sigmoid of the input."""
return 1.0 / (1.0 + math.exp(-value))
def exponential(value):
"""Return the exponential of the input."""
return math.exp(value)
# Vectorized calculation of above two functions:
sigmoid_v = np.vectorize(sigmoid)
exponential_v = np.vectorize(exponential)
Hi, I’m running your project. It looks great! From math to numpy, FPS has been greatly improved!
But now I have another problem. The nano seems to be running out of memory. The running code will report the following errors
"[TensorRT] ERROR:… /rtSafe/ safecontext.cpp (133) - Cudnn Error in configure: 7 (CUDNN_STATUS_MAPPING_ERROR)
The 2020-02-28 12:02:48. 281436: W tensorflow/core/common_runtime/bfc_allocator. Cc :211] Allocator (GPU_0_bfc) ran out of memory trying to allocate 533.62MiB. But may mean that there could be performance gains if more memory were available.
The 2020-02-28 12:02:48. 442000: W tensorflow/core/common_runtime/bfc_allocator. Cc :211] Allocator (GPU_0_bfc) ran out of memory trying to allocate 134.44MiB. But may mean that there could be performance gains if more memory were available.
The 2020-02-28 12:02:48. 496768: W tensorflow/core/common_runtime/bfc_allocator. Cc :211] Allocator (GPU_0_bfc) ran out of memory trying to allocate 134.20MiB. But may mean that there could be performance gains if more memory were available.
The 2020-02-28 12:02:48. 548342: W tensorflow/core/common_runtime/bfc_allocator. Cc :211] Allocator (GPU_0_bfc) ran out of memory trying to allocate 137.62MiB. But may mean that there could be performance gains if more memory were available."