Query Performance

[SE-Graham]

@elgs Does gosqlapi support connection pooling when using MSSQL?

I'm running very simple queries that take ~20ms when executed directly in SQL Server Management Studio. However, the same queries take ~200ms when run through gosqlapi.

That’s a consistent ~180ms overhead. Any idea what might be causing this? Could it be due to connection pooling not being enabled or configured?

The query returns a single row with a few columns, so the payload is minimal. Here’s a sample response (personal details removed):

[
  {
    "date_of_birth": "1956-10-29",
    "exceptioncodes": null,
    "forenames": "A.",
    "gender": "F",
    "hidden": "YES4",
    "known_as": "A.",
    "member_class": 6,
    "member_status": 33,
    "membership_no": "*****",
    "sbclass": null,
    "sclass": null,
    "smclass": null,
    "surname": "F."
  }
]

[elgs]

Connection pool is managed by go's sql package by default. Here is a link to some parameters of the db connection pool.

https://go.dev/doc/database/manage-connections

I can add parameters in the gosqlapi.json to tweak the pool if necessary.

Do you have the DB and gosqlapi running on the same server or separate servers?