- 최신
- 최다 투표
- 가장 많은 댓글
Hi, Thank you for using Textract and I'm sorry to hear you're facing performance issues. If you're comfortable can you share sample job IDs and the region where you're facing these issues? You can also reach out via AWS Support to share these details.
I expect the regular pattern you're seeing to the latency probably corresponds to changing overall demand on the service in the region.
Therefore I'd maybe suggest you try routing documents to a different AWS Region during these problem periods, if possible? Probably some testing would be needed to find ideal schedules & regions - but as a first guess I'd explore regions in significantly different timezones and those with high default quotas.
It's worth mentioning that for async APIs the performance characteristics for very short documents should be dominated by queuing/overheads anyway: So it's probably not that useful to compare the per-page processing time of a 200-page doc and a 1-page doc.
관련 콘텐츠
AWS 공식업데이트됨 2년 전
And as well, I found this: "underestimate because of the timed-out jobs. If you want to build a real-time, customer-facing product with PDF inputs, AWS Textract is not the tool for you. Accuracy and speed results. Double asterisks indicate the best result for each measure"Above was the answer I got from AWS support when I reported about performance. Is it true?