Github user glaksh100 commented on the issue:
The idea here is that `maxNumberOfRecordsPerFetch` should never be a value
that gets records that exceeds the read limit (2 Mb/sec) from the math here.
2 Mb/sec / (averageRecordSizeBytes * # reads/sec))
Atleast that's what the intent is - Let me know if that makes sense or if
there is something amiss about the approach here. If there is a way in which
`maxNumberOfRecordsPerFetch` is set such that the limit is exceeded, then yes,
it will still be throttled by Kinesis.