Hi @davidki
we are not counting visitors, but views. Each view results in one database entry. Not easy to say how this sums up, as the referrer and target used will differ.
But we are working on a data aggregation feature, which will remove the single entries and just saves the sum for a period of time.
See GitHub for more details.
Hope this helps!
All the best
Torsten
The answers strongly depend on some factors.
Every visit has an ID (8 Byte) and a date (3 Byte).
Plus referrer URL and request path which can vary from 0 to 255 characters (i.e. each 1020 Byte worst case)
Plus DB index overhead.
Minus potential optimization from the DB backend, both paths and referrers are often duplicated.
From a real-world site I have 4000 visits in a database with a total of 560 KiB storage (224 KiB data, 336 KIb index). So roughly 150 KiB per 1000 visits, maybe 200-250 should be a fair estimate.
(if aggregation will be there anytime in the future, the reduced size will also depend on the distribution of targets and referrers)
