Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

High usage optimization #8

Open
Pierozi opened this issue Jan 13, 2018 · 1 comment
Open

High usage optimization #8

Pierozi opened this issue Jan 13, 2018 · 1 comment
Assignees

Comments

@Pierozi
Copy link
Owner

Pierozi commented Jan 13, 2018

Regulation of buffer / offset to best performance.
Adjust sleep consumer depending of buffer size.

When we send too many request in short time, we reach error ThrottlingException (200ms on 948599 bytes chunk 1024)

@Pierozi
Copy link
Owner Author

Pierozi commented Jan 30, 2018

https://docs.aws.amazon.com/AmazonCloudWatchLogs/latest/APIReference/API_PutLogEvents.html
Constraint :

The maximum batch size is 1,048,576 bytes, and this size is calculated as the sum of all event messages in UTF-8, plus 26 bytes for each log event.

None of the log events in the batch can be more than 2 hours in the future.

None of the log events in the batch can be older than 14 days or the retention period of the log group.

The log events in the batch must be in chronological ordered by their time stamp. The time stamp is the time the event occurred, expressed as the number of milliseconds after Jan 1, 1970 00:00:00 UTC. (In AWS PowerShell Tools and the AWS SDK for .NET, the timestamp is specified in .NET format: yyyy-mm-ddThh:mm:ss. For example, 2017-09-15T13:45:30.)

The maximum number of log events in a batch is 10,000.

A batch of log events in a single request cannot span more than 24 hours. Otherwise, the operation fails.

@Pierozi Pierozi self-assigned this Jan 30, 2018
@Pierozi Pierozi mentioned this issue Feb 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant