Open kevinkupski opened 2 weeks ago
Thanks for the feedback, we’ll investigate asap.
There is currently no built-in mechanism to address this. A few possible workarounds:
@bojunehsu thank you for the feedback and the hint about json_stream. Will have a look into that. 👍
Is your feature request related to a problem? Please describe. We see high memory usage in production (which leads to Out-of-Memory-Errors) when users upload files with a lot of textual content to our app which uses Document Intelligence. For a test file with ~200.000 characters, we have 240MB in memory allocated when calling
poller.result()
, but if we extract the relevant content (strings) it's only 10 MB.It looks like the the relevant code for this is located here. Does anybody have an approach/idea to limit memory usage?
Describe the solution you'd like We'd like to reduce the data held in memory. It looks like the API does not provide this but we'd like to stream the result from Document Intelligence and process it chunk by chunk. Maybe as JSON Lines or any other streamable data format.
Describe alternatives you've considered Alternatively we only require the field
paragraphs
and could discard the rest of the response to reduce the size of the response – like a select on the fields of the response. This would not scale as good as the streaming approach, but might improve our current situation a bit.