Firebase 远程配置中的 minimumFetchInterval
minimumFetchInterval in Firebase remote config
我正在使用远程配置来提示用户进行新的更新。我应该为 minimumFetchInterval 使用什么？
问题是，如果我将这个数字保持得太低（比如 5 或 10 秒），那么它会增加对 Firebase 的调用；而且，如果我将其保留为大约 60 分钟，那么更新将延迟交付给用户。
一些意见或建议会有所帮助。
来自 throttling in Remote Config 上的 Firebase 文档：
The default and recommended production fetch interval for Remote Config is 12 hours
因此您应该在生产中将其设置为 12 小时。
来自同一页面：
During app development, you might want to refresh the cache very frequently (many times per hour) to let you rapidly iterate as you develop and test your app. To accommodate rapid iteration on a project with numerous developers, you can temporarily add a property with a low minimum fetch interval (Settings.minimumFetchIntervalMillis) in your app.
因此您可以在开发过程中将它 设置得更短，因为：
Keep in mind that this setting should be used for development only, not for an app running in production. If you're just testing your app with a small 10-person development team, you are unlikely to hit the hourly service-side quota limits. But if you pushed your app out to thousands of test users with a very low minimum fetch interval, your app would probably hit this quota.
我正在使用远程配置来提示用户进行新的更新。我应该为 minimumFetchInterval 使用什么？
问题是，如果我将这个数字保持得太低（比如 5 或 10 秒），那么它会增加对 Firebase 的调用；而且，如果我将其保留为大约 60 分钟，那么更新将延迟交付给用户。
一些意见或建议会有所帮助。
来自 throttling in Remote Config 上的 Firebase 文档：
The default and recommended production fetch interval for Remote Config is 12 hours
因此您应该在生产中将其设置为 12 小时。
来自同一页面：
During app development, you might want to refresh the cache very frequently (many times per hour) to let you rapidly iterate as you develop and test your app. To accommodate rapid iteration on a project with numerous developers, you can temporarily add a property with a low minimum fetch interval (
Settings.minimumFetchIntervalMillis) in your app.
因此您可以在开发过程中将它 设置得更短，因为：
Keep in mind that this setting should be used for development only, not for an app running in production. If you're just testing your app with a small 10-person development team, you are unlikely to hit the hourly service-side quota limits. But if you pushed your app out to thousands of test users with a very low minimum fetch interval, your app would probably hit this quota.