Bug 1918149 - Add measurements of the impact of disabing Glean event …

…batching to the docs

.dictionary

@@ -1,4 +1,4 @@
-personal_ws-1.1 en 292 utf-8
+personal_ws-1.1 en 293 utf-8
 AAR
 AARs
 ABI
@@ -257,6 +257,7 @@ substring
 swiftlint
 tcsh
 templating
+th
 timespan
 timespan's
 timespans

docs/user/user/howto/real-time-events/real-time-events.md

@@ -14,6 +14,21 @@ Glean ["events" ping](../../pings/events.md) submission can be configured either
 Setting the maximum event threshold to a value of `1` will configure the Glean SDK to submit an "events" ping for each and every [event](../../../reference/metrics/event.md) as they
 are recorded. By default, the Glean SDK will batch 500 events per "events" ping.
 
+As of November 2024, Desktop Release:
+Median user per day: 67 events / 3 pings
+The impact of turning on one event per ping based on the median user would result in an increase of approximately 21 times more event ping volume.
+
+85th percentile user per day: 305 events / 11 pings
+The impact of turning on one event per ping based on the 85th percentile user would result in an increase of approximately 26 times more event ping volume.
+
+95th percentile user per day: 706 events / 19 pings
+The impact of turning on one event per ping based on the 95th percentile user would result in an increase of approximately 36 times more event ping volume.
+
+The current release population of Desktop as a whole sends us over 10 billion events per day in over 340 million event pings. Sending each of those events as a ping would increase the ping volume by 32 times the current rate.
+
+Based on this it is safe to assume that sending 1 event per event ping would increase the ingestion traffic and downstream overhead between 20-40x the current levels with Glean batching of events in the client. This is a significant increase that should be taken into consideration before configuring Glean to disable event batching.
+
+
 ### Option 2: Using a custom ping and submitting it immediately ("Pings-as-Events")
 
 If it isn't necessary to receive all Glean SDK events that are instrumented in an application in "real-time", it may be preferable to create a