VertexAiSessionService.get_session Becomes Super Slow When There Are Higher Numbers of Session Events

[touhonoob]

Describe the bug
VertexAiSessionService.get_session Becomes Super Slow When There Are Higher Numbers of Session Events

To Reproduce
Accumulate some events for a session and get_session will start slowing down when the number of events gets higher.

Expected behavior
It should not get all events by default

[touhonoob]

Hey @DeanChensj
This issue makes the session service unusable as the response time grows linearly as the number of session events increase.
Please take a look.

[DeanChensj]

Hi @touhonoob , may I know how do you use session service? Do you use the adk api_server, or do you manage the runner yourself? I'm thinking adding configuration to only load number of recent events in session service, it will either be in the RunConfig in runner, or in the config of App

[touhonoob]

Hello @DeanChensj Thanks for checking.
I deployed my agent on Google Cloud's Vertex AI Agent Engine and didn't add any customization.
It can be easily reproduced by having a longer conversation with an ADK agent I believe.
When I checked the profiler chart it's trying to traverse through all session events pages for every single query I made, which apparently would be making it getting slower over time with growing chat history.

[touhonoob]

Maybe you guys should work on something like https://platform.openai.com/docs/api-reference/responses ?
The session service is pointless if it needs to retrieve all of the historical events

[couchrishi]

any updates pl? This is critical for production-grade deployments