-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Improve performance of eventsource parser #5862
Copy link
Copy link
Closed
Labels
ai/corecore functions like generateText, streamText, etc. Provider utils, and provider spec.core functions like generateText, streamText, etc. Provider utils, and provider spec.ai/providerrelated to a provider package. Must be assigned together with at least one `provider/*` labelrelated to a provider package. Must be assigned together with at least one `provider/*` labelfeatureNew feature or requestNew feature or request
Metadata
Metadata
Assignees
Labels
ai/corecore functions like generateText, streamText, etc. Provider utils, and provider spec.core functions like generateText, streamText, etc. Provider utils, and provider spec.ai/providerrelated to a provider package. Must be assigned together with at least one `provider/*` labelrelated to a provider package. Must be assigned together with at least one `provider/*` labelfeatureNew feature or requestNew feature or request
Type
Fields
Give feedbackNo fields configured for issues without a type.
Description
This is a follow up to #5325 (comment).
I created a simple benchmark that compares @rexxars
eventsource-parserand@ai-sdk/provider-utils' own implementation based on the bug report by @wong2:https://github.com/gr2m/eventsource-parser-benchmark/#readme
Based on this particular use case,
eventsource-parser-3.0.1iseventsource-parser-3.0.0, and@ai-sdk/provider-utils' own implementationI couldn't yet figure out where the performance difference between
eventsource-parser-3.0.1and@ai-sdk/provider-utils' own implementation is coming from. I'll look more into it this coming week