[#MDEV-14604] Profile execution of prepared statement (prepare & execute) comparing with convention execution

[MDEV-14604] Profile execution of prepared statement (prepare & execute) comparing with convention execution Created: 2017-12-07 Updated: 2018-11-22
Status:	Open
Project:	MariaDB Server
Component/s:	None
Fix Version/s:	None

Type:

Task

Priority:

Major

Reporter:

Oleksandr Byelkin

Assignee:

Unassigned

Resolution:

Unresolved

Votes:

Labels:

benchmarking

Description

We suspect that slower execution of Prepare & Execute come from double prepare and cleanup.

But probably there other places, so we need to know where the time spend.

Cases could be:
1. a lot of name resolution (many fields and tables with a lot of fields and a lot of tables)
2. no name resolution
3 ?

Comments

Comment by Oleksandr Byelkin [ 2017-12-11 ]

I got an idea. Maybe start from some well known benchmark which emulate real queries.

Comment by Oleksandr Byelkin [ 2017-12-13 ]

On first glance it is second prepare is time eater.

Generated at Thu Feb 08 08:14:52 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.