How many tracking events can we handle?

privalytics / Lean-Privalytics

Meta repository to keep track of the progress of privalytics as a company

1 stars 0 forks source link

How many tracking events can we handle? #6

Closed aquilesC closed 5 years ago

aquilesC commented 5 years ago

We can measure the time it takes to store each post request.

[x] Add Model to Log the time of each post request
[x] Use nginx to log response times
[x] Make statistics about times

aquilesC commented 5 years ago

We can also use https://locust.io/ to test the response of our server

aquilesC commented 5 years ago

I have analyzed what I have up to this point here. The tracking is not a problem (~20ms per event), but the dashboard generation consumes up to 1 second.

Tracking can easily go to 200/s (4 workers), which is 518e6 requests per month (518 advanced subscriptions).

Dashboard generation, at 1/s is still 10e6 requests per month. The problem is the inhomogeneity in time distribution, if most people visit the website at the same time ranges, etc.