The mace_cl_compiled_program.bin serves several key purposes:
Are you trying to in a MACE-based app, or are you integrating GPU tuning into your own project?
Significantly reduces model startup and inference time.
The creation and use of the mace_cl_compiled_program.bin file is an automatic process that fits into the broader MACE workflow. To get a clearer picture, let's look at the typical steps for building and running a MACE model. mace-cl-compiled-program.bin
To understand the file name itself, it helps to break it down into its core components:
So, is a pre-compiled OpenCL kernel binary that was generated by the MACE framework for a specific hardware GPU (e.g., an Adreno GPU in a Snapdragon chip, or a Mali GPU).
The file is a binary file generated by the Mobile AI Compute Engine (MACE) , a deep learning inference framework developed by Xiaomi . This specific file contains compiled OpenCL kernels and tuned parameters optimized for a specific mobile device's GPU. The mace_cl_compiled_program
When MACE initializes a model (e.g., a neural network for camera scene detection), it checks for the existence of mace-cl-compiled-program.bin .
If you are encountering a specific error while deploying this framework, let me know the , the System-on-Chip (SoC) powering it, and the exact console logs you receive. I can help you debug the explicit OpenCL kernel parameters. Share public link
Depending on how many AI models and distinct GPU kernels an app uses, this file can grow from a few megabytes to dozens of megabytes. While it might look like a waste of space, the performance and battery-saving benefits far outweigh the minor storage cost. To get a clearer picture, let's look at
mace-cl-compiled-program.bin is a binary file associated with , specifically tied to the Computer Vision (CV) and Neural Processing (NP) pipelines on Snapdragon SoCs (System on Chips). The "CL" in the name strongly indicates OpenCL (Open Computing Language) compilation.
When users use backup-and-restore tools to migrate their application data from an old smartphone to a completely new hardware platform, the app data directory—including mace-cl-compiled-program.bin —is copied over.
The file is typically found on the device within the app’s internal storage or public storage, often named mace_cl_compiled_program.bin or similar, as seen in various GitHub MACE issues . Generating the File: The "Tuner" Component
// Run inference std::map<std::string, mace::MaceTensor> inputs, outputs; // ... fill inputs engine->Run(inputs, &outputs);
Tap (Do not tap "Clear Data" unless you want to reset the app entirely). Method 2: Manual Deletion via File Manager