Hey team. We're in evaluation mode and have just kicked off a test AB test, but we're seeing a higher number of "CDN Requests" than we anticipated. We currently have around 4000 users in the AB test, but we're seeing north of 200k CDN requests per day on the Swift SDK. We have verified that we establish one growthbook client per logged in session, so that's not the issue. We do however have backgroundSync turned on. Two questions based off that context 1. How does backgroundSync relate to the CDN requests quota? Is it treated as one request to establish a subscription, or is each sync message sent being treated as a CDN request?

Regarding this question about backgroundSync and CDN requests - I've checked with the team, and we're waiting for clarification on how SSE connections and reconnects are counted toward the CDN quota. I'll get back to you as soon as I have an answer.

Hello @brash-afternoon-80519,

backgroundSync

in the Swift SDK uses a long-lived SSE subscription for streaming updates. Which means, • Opening the stream is an HTTP request and messages delivered over that already-open stream are NOT separate HTTP requests. • If the stream disconnects and reconnects, each reconnect is a new request. That’s why request volume can be much higher than your concurrent user count. so, 4,000 users can absolutely generate 200k+ requests/day if those clients stay active for a while and the stream reconnects periodically. If you don’t need flags to update in real time during a session, try the manual approach of managing features or use offline mode. Hope this helps.

Thanks @freezing-postman-69602 this really helps