Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

🔧 Use ObjectPools for chat request/response schemas #262

Open
roma-glushko opened this issue May 19, 2024 · 1 comment
Open

🔧 Use ObjectPools for chat request/response schemas #262

roma-glushko opened this issue May 19, 2024 · 1 comment
Assignees
@tom-fitz
Labels
area:api area:routing good first issue Good for newcomers help wanted Extra attention is needed type:enhancement New feature or request

Comments

@roma-glushko
Copy link
Member

Use ObjectPools to optimize memory allocation of

  • chat request/response schema allocations
  • chat stream chunk schema allocations
@roma-glushko roma-glushko added type:enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed area:api area:routing labels May 19, 2024
@roma-glushko roma-glushko changed the title Use ObjectPools for chat request/response schemas 🔧 Use ObjectPools for chat request/response schemas May 19, 2024
@tom-fitz
Copy link
Contributor

@roma-glushko Could you assign this one to me? I've got a PR up for the first part, and will start working on streaming.

@roma-glushko roma-glushko linked a pull request Jun 13, 2024 that will close this issue
🔧 #262: adding connection pool for chat request and response #271
Merged
@roma-glushko roma-glushko removed a link to a pull request Jun 13, 2024
🔧 #262: adding connection pool for chat request and response #271
Merged
roma-glushko pushed a commit that referenced this issue Jun 13, 2024
@tom-fitz
🔧 #262: adding connection pool for chat request and response (#271)
0bb4878 
Basic implementation of connection pooling for chat functionality.
@roma-glushko roma-glushko mentioned this issue Jun 24, 2024
Merged
roma-glushko added a commit that referenced this issue Jun 24, 2024
@roma-glushko
📦 Release: v0.1.0-rc.1 (#280)
1e2b16f 
The first major update with breaking changes to the language chat schemas 
and begging of work on instrumenting the gateway with OpenTelemetry.

### Added

- 🔧 Use github.com/EinStack/glide as module name to support go install cmd (@gernest)
- ✨🔧 Setup Open Telemetry Metrics and Traces (#237) (@gernest)
-  🔧 #221 Add B3 trace propagator (#242) (@gernest)
- 🔧 #241 Support overriding OTEL resource attributes (#243) (@gernest)
- 🔧 #248 Disable span and metrics by default (#254) (@gernest)
- 🔧 #220 Instrument API server with observability signals (#255) (@gernest)
- 🔧 #164 Make client connection pool configurable across all providers (#251) (@daesu)
- 🔧 Instrument gateway process (#256) (@gernest)
- 🔧 #262: adding connection pool for chat request and response (#271) (@tom-fitz)

### Changed

- 🔧 #238 Implements human-readable durations in config (#253) (@ppmdo)
- 🔧 #266: removing omitempty from response definition (#267) (@tom-fitz)

#### Breaking Changes

- 🔧 💥 #235: Extended the non-streaming chat error schema with new fields to give clients more context around the error (#236) (@roma-glushko)
- 💥 Convert all camelCase config fields to the snake_case in the provider configs (#260) (@roma-glushko)
- ✨💥 #153: Allow to pass multiple model-specific param overrides (#264) (@roma-glushko)

### Fixed

- 🐛 #217: Set build info correctly in Glide images (#218) (@roma-glushko)

### Security

- 🔒 Updated golang to 1.22.4 to address CVE-2024-24790 (#276) (@STAR-173)

### Miscellaneous

- 📝 Defined a way to manage EinStack Glide project (#234) (@roma-glushko)
- 👷 #219: Setup local telemetry stack with Jaeger, Grafana, VictoriaMetrics and OTEL Collector (#225) (@roma-glushko)
- 👷‍♂️ Added a new GH action to watch for glide activity stream (#239, #244) (@roma-glushko)
- ✨ Switched to the new docs (@roma-glushko)
- 🔧 #240: Automatically install air (#277, #270) (@ppmdo, @roma-glushko)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tom-fitz tom-fitz

Labels
area:api area:routing good first issue Good for newcomers help wanted Extra attention is needed type:enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@roma-glushko @tom-fitz