Proxy Configuration via Environment Variables and Global Request Sessions #3637

New Issue

2025-11-11T15:35:55-06:00

GiteaMirror commented

2025-11-11 15:35:55 -06:00

Originally created by @ashm-dev on GitHub (Feb 6, 2025).

Description

Hello!

I would like to propose two enhancements to improve performance and simplify the codebase:

Proxy Configuration via Environment Variables
Enable the ability to configure proxies through environment variables, for example: PROXY=protocol://ip:port
Global Request Sessions
Implement global sessions for both aiohttp and requests. This approach would offer several advantages:

Connection Reuse:
Reusing the TCP connection pool will reduce the overhead of establishing new connections, thereby speeding up request processing.
Centralized Configuration:
Managing session settings (such as headers, timeouts, proxies, etc.) in a single location simplifies maintenance and ensures consistency across the application.
Code Simplification:
A global session reduces the need to repeatedly initialize and manage individual sessions, leading to cleaner and more maintainable code.

Benefits

Improved Performance:
By reusing TCP connections, the application can handle requests more efficiently.
Easier Maintenance:
Centralizing session configurations simplifies adjustments and reduces the risk of inconsistencies.
Reduced Code Complexity:
Fewer session initializations and closures make the codebase easier to understand and maintain.

Thank you for considering this proposal!

Originally created by @ashm-dev on GitHub (Feb 6, 2025). #### Description Hello! I would like to propose two enhancements to improve performance and simplify the codebase: 1. **Proxy Configuration via Environment Variables** Enable the ability to configure proxies through environment variables, for example: `PROXY=protocol://ip:port` 2. **Global Request Sessions** Implement global sessions for both aiohttp and requests. This approach would offer several advantages: - **Connection Reuse:** Reusing the TCP connection pool will reduce the overhead of establishing new connections, thereby speeding up request processing. - **Centralized Configuration:** Managing session settings (such as headers, timeouts, proxies, etc.) in a single location simplifies maintenance and ensures consistency across the application. - **Code Simplification:** A global session reduces the need to repeatedly initialize and manage individual sessions, leading to cleaner and more maintainable code. #### Benefits - **Improved Performance:** By reusing TCP connections, the application can handle requests more efficiently. - **Easier Maintenance:** Centralizing session configurations simplifies adjustments and reduces the risk of inconsistencies. - **Reduced Code Complexity:** Fewer session initializations and closures make the codebase easier to understand and maintain. Thank you for considering this proposal!

GiteaMirror closed this issue

2025-11-11 15:35:55 -06:00

GiteaMirror referenced this issue

2026-04-19 20:06:15 -05:00

[GH-ISSUE #3637] GPU Index Out of Bounds Error During Vector Search in RAG Module #13331

GiteaMirror referenced this issue

2026-04-25 03:23:56 -05:00

[GH-ISSUE #3637] GPU Index Out of Bounds Error During Vector Search in RAG Module #28859

GiteaMirror referenced this issue

2026-05-05 13:13:45 -05:00

[GH-ISSUE #3637] GPU Index Out of Bounds Error During Vector Search in RAG Module #51997

GiteaMirror referenced this issue