-
Notifications
You must be signed in to change notification settings - Fork 50
Lots of calls to sp_describe_undeclared_parameters #610
Copy link
Copy link
Open
Labels
area: performanceThroughput, latency, GIL retention, large-param slowness, expensive round-trips, perf-regressionsThroughput, latency, GIL retention, large-param slowness, expensive round-trips, perf-regressionsbugSomething isn't workingSomething isn't workinginADOtriage doneIssues that are triaged by dev team and are in investigation.Issues that are triaged by dev team and are in investigation.
Metadata
Metadata
Assignees
Labels
area: performanceThroughput, latency, GIL retention, large-param slowness, expensive round-trips, perf-regressionsThroughput, latency, GIL retention, large-param slowness, expensive round-trips, perf-regressionsbugSomething isn't workingSomething isn't workinginADOtriage doneIssues that are triaged by dev team and are in investigation.Issues that are triaged by dev team and are in investigation.
Type
Fields
Give feedbackNo fields configured for Bug.
Any time a parameterized query sends a
None, I'm seeing an internal call made tosp_describe_undeclared_parameters. Since my workload is entirely parameterized and sends a lot of Nones in the course of its work, I'm getting thousands of these calls a minute. I'm sure that's adding up to a significant performance hit in aggregate.To make matters worse, the vast majority of these calls are internally throwing an exception, so I'm not sure how much value they're providing in general to the driver. For example, if a stored procedure is called with named parameters, the call will fail with a message like: "@first_parameter is not a parameter for procedure my_stored_procedure."
So, I guess I'd like to ask a few things: