getTranscript performance is slow

[Hesham-Salama]

Not sure if it's a problem in SDK but the performance of the call of getTranscript(:) https://docs.aws.amazon.com/connect/latest/APIReference/API_connect-participant_GetTranscript.html is slow.

To Reproduce
Steps to reproduce the behavior:

1. Just call - (AWSTask<AWSConnectParticipantGetTranscriptResponse *> *)getTranscript(AWSConnectParticipantGetTranscriptRequest *)request; which belongs to @interface AWSConnectParticipant

The performance is the same for both ENTIRE_PAST_SESSION and FROM_SEGMENT passed in RehydrationType. https://docs.aws.amazon.com/connect/latest/APIReference/API_PersistentChat.html#connect-Type-PersistentChat-SourceContactId

Observed Behavior
It takes at least 0.5 seconds per call / chat page retrieval.

Expected Behavior
The call should retrieve the transcripts much faster.

Environment(please complete the following information):

• SDK Version: 2.33.8
• Swift Version : 5
• Xcode Version: 15.4

Device Information (please complete the following information):

• Device: iPhone15, Simulator
• iOS Version: 17.5

Maybe out of the topic, but I've also noticed the hydration process is slow as well.

[Hesham-Salama]

Used region: London EU-WEST-2

[harsh62]

@Hesham-Salama Thanks for raising the issue. Our team will look into it and provide update when we have one.

[tylerjroach]

The call should retrieve the transcripts much faster.

Hi @Hesham-Salama,

Is the speed expectation for these calls based on seeing faster performance on other platforms? Our client SDKs can't control the request times of the AWS services being hit, but if you are seeing significant differences between the iOS SDK vs another one of our SDKs, please let us know.

[Hesham-Salama]

@tylerjroach I have just tried the API in postman POST /participant/transcript.

It seems the response time range is the same between the SDK and API. Honestly I think 621ms is too long and that's per page.

[tylerjroach]

@Hesham-Salama You will need to reach out to the Connect team if you have performance concerns on the API itself. Our SDKs cannot control the speed at which various service APIs respond.

[github-actions]

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.