Performance pitfall when prepare flag is set and parameters is null

Description

Routing logic tries to evaluate and encode parameters when the statement is prepared, without considering that can be null, causing a significant degradation in performance for this particular case.

Environment

None

Pull Requests

None

Activity

Show:
Jorge Bay Gondra
February 13, 2020, 3:50 PM

I’ve been looking at it, trying to make sense at the issue and I couldn’t find the culprit as described in the ticket.

I’ve run benchmarks with and without null parameters and I couldn’t find anything suspicious (charts attached). I’m closing this one as cannot reproduce.

Cannot Reproduce

Assignee

Unassigned

Reporter

Jorge Bay Gondra

Reviewer

None

Fix versions

None

Labels

Components

None

PM Priority

None

Reproduced in

None

Pull Request

None

Priority

Major
Configure