AsyncSession multithreading sometimes takes 15 minutes to query PostgreSQL database

[liquor96]

\langflow\services\database\service.py

@asynccontextmanager
async def with_session(self):
async with AsyncSession(self.engine, expire_on_commit=False) as session:
yield session

Do we need to use async_sessionmaker like this：
from sqlalchemy.ext.asyncio import async_sessionmaker

class DatabaseService(Service):
name = "database_service"

def __init__(self, settings_service: SettingsService):
    # 现有初始化代码...
    self.engine = self._create_engine()
    self.AsyncSessionFactory = async_sessionmaker(
        bind=self.engine,
        expire_on_commit=False,
        class_=AsyncSession
    )

@asynccontextmanager
async def with_session(self):
    logger.error(f"[request_log] - Creating new session start")
    start_time = time.perf_counter()
    async with self.AsyncSessionFactory() as session:
        logger.error(f"[request_log] - Creating new session cost time:{int(time.perf_counter() - start_time)}")
        yield session

[dosubot[bot]]

Using async_sessionmaker can be beneficial for managing sessions in a more efficient and consistent manner, especially when dealing with asynchronous operations. The async_sessionmaker provides a factory for creating AsyncSession instances, which can help streamline session management and potentially improve performance.

In your current implementation, you're directly creating an AsyncSession in the with_session method. Switching to async_sessionmaker as shown in your example can help by centralizing the session creation logic and potentially reducing overhead when creating new sessions.

Here's a brief explanation of the changes:

1. Initialization: You create an AsyncSessionFactory using async_sessionmaker, which binds to the engine and sets expire_on_commit to False.

2. Session Management: In the with_session method, you use this factory to create sessions. This can help ensure that all sessions are created with the same configuration and can improve consistency across your application.

This change might help address the performance issues you're experiencing with multithreading and querying the PostgreSQL database. It can also make your code cleaner and more maintainable by encapsulating session creation logic within the factory.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}