• Resolved davidki

    (@davidki)


    Hello,

    can you tell approximately how the database size will change, lets say, after 100,000 visitors are recorded?

    How many rows are created and how much will the database increase in kilobits?

    Thank you,

    david

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Torsten Landsiedel

    (@zodiac1978)

    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

    Plugin Support Stefan Kalscheuer

    (@stklcode)

    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)

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Database size’ is closed to new replies.