Change Details

The reading team asked if it would be possible to increment the rate of events per second of the Popups schema over 10/sec without having to blacklist the schema for mysql insertion. They would do it during 2 weeks starting in around 2 weeks from now [PENDING CONFIRMATION] Their initial wish is to have 100 evt/sec, which would result in a total of 120M events for the 2 weeks, and given the rather big size of the Popups schema, this would occupy around 240GB on disk. We can assess if that is too much and negotiate on a lower sampling rate, or other potential solutions.

The reading team asked if it would be possible to increment the rate of events per second of the Popups schema over 10/sec without having to blacklist the schema for mysql insertion. They would do it during 2 weeks starting in around 2 weeks from now [PENDING CONFIRMATION] and after this time passed, the schema would return to its normal <10evt/sec. Their initial wish is to have 100 evt/sec, which would result in a total of 120M events for the 2 weeks, and given the rather big size of the Popups schema, this would occupy around 240GB on disk. We can assess if that is too much and negotiate on a lower sampling rate, or other potential solutions.

The reading team asked if it would be possible to increment the rate of events per second of the Popups schema over 10/sec without having to blacklist the schema for mysql insertion. They would do it during 2 weeks starting in around 2 weeks from now [PENDING CONFIRMATION] and after this time passed, the schema would return to its normal <10evt/sec. Their initial wish is to have 100 evt/sec, which would result in a total of 120M events for the 2 weeks, and given the rather big size of the Popups schema, this would occupy around 240GB on disk. We can assess if that is too much and negotiate on a lower sampling rate, or other potential solutions.