(cc-ing Amir)
>
> [sean] Is there a plan for purging old data from this one?
>[christian]Just to make expectations explicit:
>[christian] Since in a different part of this thread you are asking more for
>[christian] expected growth bounds, I assume that the table can stay at that size
>[christian] until discussion with Language about the way forward produced concrete
>[christian] next steps, and you do not expect us to prune data right away.
So we are all on the same page, the table has a lot of data cause i18n team was not aware logging was happening until we notify them of that fact. As Amir mentioned, the bug that prompted the logging has been fixed. As Dario said we definitely do not need that much data.
I confirmed last week that we only need to 2 weeks of data to analyze, the data is just a short "survey" of what our users have available when it comes to fonts. So, yes, we could delete a bunch of the data and I believe Amir was about to request us to do so.
Since I have no permits to create tables, could we create a temporary table that holds the last two weeks of data? We could use that for our analysis and get rid of the other table once the bugfix is in production and logging has stopped.
>[sean] I'm interested in identifying the expected growth bounds rather than limiting tables arbitrarily.
This is definitely an item on our court, we need to determine those bounds and throttle when they are exceeded.
We do not have any throttling when it comes to record creation. We detect the higher throughput of data but that's about it.
I have created a backlog item to this extent: