The docs say we can delete the source .aimodel after a .persistent specialize and keep the bookmark to save space. But an OS update always invalidates the cache and bookmarks, so it looks like anyone who deleted the source has to re-download the whole model after every update. For large models, that's a lot of bandwidth and impacts the first-time experience after the update. Is that the intended trade-off, or does the cache hold enough to re-specialize itself?
Does every minor OS bumps (27.1 -> 27.2) always invalidate cache when .persisted, or only major ones?
Also, can the user delete a .persistent entry themselves through Settings or storage management, or only the app? We need to know whether our "model is ready" state can disappear without the app knowing.
The docs say we can delete the source .aimodel after a .persistent specialize and keep the bookmark to save space. But an OS update always invalidates the cache and bookmarks, so it looks like anyone who deleted the source has to re-download the whole model after every update. For large models, that's a lot of bandwidth and impacts the first-time experience after the update. Is that the intended trade-off, or does the cache hold enough to re-specialize itself?
To specialize a model we do require the source .aimodel or .aimodelc, the specialized asset does not hold the information contained in the source needed for specialization.
Does every minor OS bumps (27.1 -> 27.2) always invalidate cache when .persisted, or only major ones?
Correct, a specialized asset is tied directly to the specific OS (major & minor) version used to generate it.
Also, can the user delete a .persistent entry themselves through Settings or storage management, or only the app? We need to know whether our "model is ready" state can disappear without the app knowing.
Deletion would need to occur through the application.
