Bureaucrats, dave_user, Administrators
4,650
edits
Changes
no edit summary
* All the files required to run the test—the executable, the image files, etc.—are stored on a [https://www.jamescoyle.net/how-to/943-create-a-ram-disk-in-linux tmpfs RAM disk] in order to make file system/storage medium overhead neglectable.
=== Version 1 (no NPU acceleration) ===
The following sections detail the execution of the first version of the classifier on the embedded platform. The number of threads was also tweaked in order to test different configurations. During the execution, the well-known <code>[https://en.wikipedia.org/wiki/Htop htop]</code> utility was used to monitor the system. This tool is very convenient to get some useful information such as cores allocation, processor load, and number of running threads.
==== Floating-point model ====
The following dump refers to the execution of the application.<pre class="board-terminal">
root@imx8mpevk:/mnt/ramdisk/image_classifier_eIQ_plus# build/image_classifier_cv 2 my_converted_model.tflite labels.txt testdata/red-apple1.jpg
Number of threads: undefined
====Half-quantized model ====
The following dump refers to the execution of the application in combination with the half-quantized model.<pre class="board-terminal">
root@imx8mpevk:/mnt/ramdisk/image_classifier_eIQ_plus# build/image_classifier_cv 2 my_fruits_model_1.12_quant.tflite labels.txt testdata/red-apple1.jpg
Number of threads: undefined
The following screenshot shows the system status while executing during the applicationexecution. In this case, the thread parameter was unspecified.
