Azure Cosmos DB - 对运行状况检查项目使用非常低的 TTL 有什么缺点吗？
Azure Cosmos DB - any downside of using very low TTL for health check items?
作为我们为应用程序实施的健康检查的一部分，我们正在尝试将虚拟文档写入数据库。对于此文档，我们使用 10 秒的 TTL（生存时间），以便 Cosmos DB 自动清理文档。
我的问题是：将 TTL 一直设置为 1 秒是否有缺点（性能、RU 成本等）？文档一写成功，健康检查就开心了，我们也不管文档了
设置低 TTL 没有任何缺点、性能下降或额外成本。
如果您查看此文档 HERE。它指出。
Deletion of expired items is a background task that consumes left-over
Request Units, that is Request Units that haven't been consumed by
user requests. Even after the TTL has expired, if the container is
overloaded with requests and if there aren't enough RU's available,
the data deletion is delayed. Data is deleted once there are enough
RUs available to perform the delete operation. Though the data
deletion is delayed, data is not returned by any queries (by any API)
after the TTL has expired.
作为我们为应用程序实施的健康检查的一部分，我们正在尝试将虚拟文档写入数据库。对于此文档，我们使用 10 秒的 TTL（生存时间），以便 Cosmos DB 自动清理文档。
我的问题是：将 TTL 一直设置为 1 秒是否有缺点（性能、RU 成本等）？文档一写成功，健康检查就开心了，我们也不管文档了
设置低 TTL 没有任何缺点、性能下降或额外成本。 如果您查看此文档 HERE。它指出。
Deletion of expired items is a background task that consumes left-over Request Units, that is Request Units that haven't been consumed by user requests. Even after the TTL has expired, if the container is overloaded with requests and if there aren't enough RU's available, the data deletion is delayed. Data is deleted once there are enough RUs available to perform the delete operation. Though the data deletion is delayed, data is not returned by any queries (by any API) after the TTL has expired.