My App is an App based on CloudKit technology that helps users match each other in real time, so it relies heavily on CloudKit's service stability. One of the problems that happened in the past few days is that CloudKit's public database index generation became very slow, and the data generated by one user could be queried by another user in a few seconds before, now it takes nearly a minute. This makes it impossible for my app users to do real-time matching with this technology.
- Using an AppleID, create a CKRecord containing several items of data, save it to the defaultZone of the public database, and create QueryIndex for these items.
- Immediately use another AppleID to Query this record in the defaultZone with these data.
- Check how long to wait before this record is queried.
- Under normal circumstances, the database index should be built very quickly, taking less than 5 seconds to query the corresponding record.
- In fact this process is currently becoming so slow that I am currently spending up to a minute waiting to query this record.
Besides, my app is mainly operated in China, please also check if only Guizhou on the Cloud will have such problem.
----- Chinese Translate
我的 App 是一个基于 CloudKit 技术，帮助用户实时互相匹配的 App。所以非常依赖 CloudKit 的服务稳定性 这几天发生的一个问题是，CloudKit 的公共数据库索引生成变得非常缓慢，之前一个用户生成的数据，另一个用户几秒钟就可以查询到，现在需要花费近1分钟 这就导致我的 App 用户无法通过这个技术完成实时匹配了
- 使用一个 AppleID，创建一个包含了几项数据的 CKRecord，保存到公共数据库的 defaultZone，并创建这几个数据的 QueryIndex
- 立即使用另一个 AppleID，在 defaultZone 中使用这几项数据 Query 这个 record
- 检查需要等待多久，这个 record 才会被查询到
- 正常情况下，数据库的索引建立应该很快，只需要花费不到5秒就可以 Query 到对应 record
- 实际上这个过程目前变得非常缓慢，我目前需要花费长达1分钟的等待时间才能查询到这个 record
另外我的 App 主要在中国运营，也请检查是不是只有云上贵州会有这样的问题
