It seems likely that searching sessions by message content in Phoenix can be slow, especially as data size grows, due to how the backend queries are structured and the lack of full-text indexing or optimizations for large attributes. There are known reports of slow GraphQL queries and suggestions to avoid pulling large attributes over connections, as this can significantly impact performance鈥攅ven with moderate data sizes. Some improvements have been made (e.g., reducing page size, lazy loading), but searching message content remains a bottleneck if the session or span attributes are large or not indexed for text search. My understanding is that, as of now, there are no user-configurable settings to speed up this specific search, and the slowness is a recognized limitation in the current implementation (<https://github.com/Arize-ai/phoenix/issues/4006|source>, <https://arize-ai.slack.com/archives/C04R3GXC8HK/p1718305854.864919|source>, <https://github.com/Arize-ai/phoenix/pull/5204|source>).
Possible workarounds mentioned include limiting the size of stored messages, using previews instead of full content, or offloading large messages to blob storage and storing only references in Phoenix. There is no mention in the data sources of a direct way to enable full-text search or indexing for session messages, nor a configuration to speed up these queries in the UI or backend. Would you like more detail on the technical reasons for this slowness or on potential architectural workarounds?
Sources:
- <https://github.com/Arize-ai/phoenix/issues/4006|github.com/Arize-ai/phoenix/issues/4006>
- <https://arize-ai.slack.com/archives/C04R3GXC8HK/p1718305854.864919|arize-ai.slack.com/archives/C04R3GXC8HK/p1718305854.864919>
- <https://github.com/Arize-ai/phoenix/pull/5204|https://github.com/Arize-ai/phoenix/pull/5204>
