私的AI研究会 > OpenVINO Tips2
例:export cl_cache_dir=$HOME/run_app/cl_cache
デモタイトル | CPU | キャッシュなし | キャッシュあり | キャッシュ・サイズ | ||
GPU (FP16) | GPU (FP32) | GPU (FP16) | GPU (FP32) | MB | ||
アクション認識 Python デモ human_pose_estimation_3d_demo | 1.5s | 47s | 46.3s | 1.45 | 1.4s | 1.0 |
テキスト検出 C++ デモ text_detection_demo | 2s | 10m44s | 10m40s | 4.5s | 4.4s | 9.5 |
What are the known limitations of cl_cache? 1. Not thread safe. (Workaround: Make sure your clBuildProgram calls are executed in thread safe fashion.) 2. Binary representation may not be compatible between various versions of NEO and IGC drivers. (Workaround: Manually empty cl_cache directory prior to update) 3. Cache is not automatically cleaned. (Workaround: Manually empty cl_cache directory) 4. Cache may exhaust disk space and cause further failures. (Workaround: Monitor and manually empty cl_cache directory) 5. Cache is not process safe.