PCC rate limits and blocking Siri AI as a result

Machine Learning & AI Foundation Models
2greggy OP
Created
Replies 4
Boosts 0
Views 1.2k
Participants 1

Hello,

I have PCC deployed in my 3 apps and my testing for these apps has caused me to hit the rate limit many times. When this rate limit is hit, Siri AI (as well as HomeKit PCC features) stops working completely for me until the rate limit is reset.

I have been forced to scale back PCC and testing in my apps as this situation is quite opaque. My logs say I’m being rate limited when using PCC in these cases.

Example log I see: 10:51:47.407 | RemoteManager executing remote streaming request 10:51:47.407 ModelCatalog | Looking up asset bundle com.apple.fm.language.instruct_server_v2.fm_api in Model Catalog 10:51:47.410 DaemonSession | Asset com.apple.fm.language.instruct_server_v2.fm_api has inference providers: 10:51:47.410 DaemonSession | - private-ml-client 10:51:47.411 ExecutionGroup | executing request C9B08798-6D68-4819-83C9-89B2EF5278C4 10:51:47.431 InferenceProviderConnection | InferenceProvider requestInference (C9B08798-6D68-4819-83C9-89B2EF5278C4) finished 10:51:47.431 RemoteManager | Request failed on private-ml-client with error: InferenceError::rateLimited::PrivateCloudComputeError: deniedDueToUserDeviceRateLimit, falling back 10:51:47.431 RemoteIPC Tasks | Failed to execute remote streamingRequest with error: InferenceError::rateLimited::PrivateCloudComputeError: deniedDueToUserDeviceRateLimit 10:51:56 modelmanagerd [com.apple.modelmanager:RemoteIPC Tasks] Failed to execute remote oneShotRequest with error: InferenceError::rateLimited::PrivateCloudComputeError: deniedDueToUserDev 11:23:39 privatecloudcomputed [com.apple.privatecloudcompute:RateLimiter] rate limit applied from cached denials

What are the rate limits? How many requests a day? Per second?

Also, I subscribed to the highest iCloud storage tier in hopes of higher rate limit but there doesn't seem to be any change.

https://support.apple.com/en-us/127901

This issue started when iOS27 became publicly available - I was never rate limited when on the iOS27 beta.

Answered by 2greggy in 912709022

The issue appears be resolved. The fix was either a server side change, AppleOS27 or both.

Replies  4
Boosts 0
Views  1.2k
Participants  1
2greggy OP

I think I found part of the culprit - I woke up today with Siri AI not working - not even the light control works. Nothing of mine should have been hitting PCC so I checked the Apple TV that is the home hub that uses PCC for video clips:

  • What it sends: mediaanalysisd on the TV analyses HomeKit camera clips and routes each one to "Pro". The number of clips routed per hour matches the TV's completed PCC requests hour for hour (43, 63, 70, 43, 13, 15, 25 and 29 from 04:00 to 11:00).
  • Why every clip goes: The routing threshold is THR=0.0000, so everything goes to the cloud. 4,213 of 4,291 routed clips had no person, pet, vehicle or package, all with the same score of 0.2115. That looks like wind-triggered motion.
  • Volume: 694 clips in the last 24 h, against a daily limit its daemon was told about (rate limit discovered: count=500, duration=86400). Oct 2 had 1,442. Today's 351 requests since 03:00 all ended in errors 32080/32081.

Its been a windy day so there are more than normal recording on an average day but this feature on Apple TV - is it intended to block PCC for my entire iCloud account for video events? Is this intentional or a bug? Should I be disabling summarized videos completely to avoid this?
2greggy OP

Turning summaries off seems to help.
2greggy OP

I confirm this behavior continues with all devices updated to 27.2 RC. Vision Pro even states that I'm out of requests even though I just put my Vision Pro on for the first time today and made a single Siri request.

Yesterday I enabled the camera summaries in HomeKit after installing 27.2 RC to see if the behavior corrected but it still persists. HomeKit camera PCC requests should be separate from actual Siri AI use since its a paid feature.
2greggy OP
Accepted Answer

The issue appears be resolved. The fix was either a server side change, AppleOS27 or both.