Details
-
Task
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
Description
It seems there is an issue when querying on I_S.PARAMETERS table (used in java metadata) :
when doing this kind of query (one result) :
SELECT * FROM INFORMATION_SCHEMA.PARAMETERS WHERE SPECIFIC_SCHEMA = 'testj' AND SPECIFIC_NAME = 'p2_512'
It takes 15ms if 400 parameters in I_S.PARAMETERS table
It takes 65ms if 4K parameters
It takes 350ms if 20K parameters
It seems to execute a full table scan in INFORMATION_SCHEMA.PARAMETERS
The same query takes 6ms on mysql 8 with 20K same parameters
Attachments
Issue Links
- causes
-
CONJ-684 Performance of con.getMetaData().getProcedureColumns(null, null, name, "%") is much lower than mysql jdbc
-
- Closed
-
-
MDEV-29550 Valgrind/MSAN uninitialised value errors upon SHOW PROCEDURE STATUS with condition on Db
-
- Closed
-
-
MDEV-29858 Missing DBUG_RETURN or DBUG_VOID_RETURN macro in function "fill_schema_proc"
-
- Closed
-
- is part of
-
MDEV-29547 prepare 10.11.0 preview releases
-
- Closed
-
- relates to
-
MDEV-28979 Feature Request: Allow for indexes to be created on the information_schema tables
-
- Closed
-
-
MDEV-29104 Performance Issues Reading information_schema.PARAMETERS
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Description |
It seems there is an issue when querying on I_S.PARAMETERS table (used in java metadata) :
when doing this kind of query (one result) : SELECT * FROM INFORMATION_SCHEMA.PARAMETERS WHERE SPECIFIC_SCHEMA = 'testj' AND SPECIFIC_NAME = 'p2_512' It takes 15ms if 400 parameters in I_S.PARAMETERS table It takes 65ms if 4K parameters It takes 350ms if 20K parameters The same query takes 6ms on mysql 8 with 20K same parameters |
It seems there is an issue when querying on I_S.PARAMETERS table (used in java metadata) :
when doing this kind of query (one result) : SELECT * FROM INFORMATION_SCHEMA.PARAMETERS WHERE SPECIFIC_SCHEMA = 'testj' AND SPECIFIC_NAME = 'p2_512' It takes 15ms if 400 parameters in I_S.PARAMETERS table It takes 65ms if 4K parameters It takes 350ms if 20K parameters It seems to execute a full table scan in INFORMATION_SCHEMA.PARAMETERS The same query takes 6ms on mysql 8 with 20K same parameters |
Component/s | Server [ 13907 ] | |
Fix Version/s | 10.1 [ 16100 ] | |
Fix Version/s | 10.2 [ 14601 ] | |
Fix Version/s | 10.3 [ 22126 ] | |
Fix Version/s | 10.4 [ 22408 ] | |
Assignee | Oleksandr Byelkin [ sanja ] |
Attachment | screenshot-1.png [ 53698 ] |
Attachment | screenshot-2.png [ 53699 ] |
Fix Version/s | 10.5 [ 23123 ] |
Fix Version/s | 10.1 [ 16100 ] |
Labels | CONNECTOR_RELATED |
Comment | [ On first glance, it seems {{calc_lookup_values_from_cond}} can be used to infer the lookup value. ] |
Comment | [ On first glance, it seems {{calc_lookup_values_from_cond}} can be used to infer the lookup value. ] |
Comment | [ On first glance, it seems {{calc_lookup_values_from_cond}} can be used to infer the lookup value. ] |
Workflow | MariaDB v3 [ 99707 ] | MariaDB v4 [ 141542 ] |
Priority | Major [ 3 ] | Critical [ 2 ] |
Priority | Critical [ 2 ] | Major [ 3 ] |
Status | Open [ 1 ] | Confirmed [ 10101 ] |
Link |
This issue relates to |
Priority | Major [ 3 ] | Critical [ 2 ] |
Status | Confirmed [ 10101 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | Stalled [ 10000 ] |
Fix Version/s | 10.11 [ 27614 ] | |
Fix Version/s | 10.2 [ 14601 ] | |
Fix Version/s | 10.3 [ 22126 ] | |
Fix Version/s | 10.4 [ 22408 ] | |
Fix Version/s | 10.5 [ 23123 ] |
Affects Version/s | 10.2 [ 14601 ] | |
Affects Version/s | 10.3 [ 22126 ] | |
Affects Version/s | 10.4 [ 22408 ] | |
Issue Type | Bug [ 1 ] | Task [ 3 ] |
Assignee | Oleksandr Byelkin [ sanja ] | Sergei Petrunia [ psergey ] |
Link |
This issue relates to |
Attachment | mdev20609.diff [ 64903 ] |
Assignee | Sergei Petrunia [ psergey ] | Oleg Smirnov [ JIRAUSER50405 ] |
Status | Stalled [ 10000 ] | In Progress [ 3 ] |
Summary | Full table scan in INFORMATION_SCHEMA.PARAMETERS | Full table scan in INFORMATION_SCHEMA.PARAMETERS |
Summary | Full table scan in INFORMATION_SCHEMA.PARAMETERS | Full table scan in INFORMATION_SCHEMA.PARAMETERS/ROUTINES |
Assignee | Oleg Smirnov [ JIRAUSER50405 ] | Sergei Petrunia [ psergey ] |
Status | In Progress [ 3 ] | In Review [ 10002 ] |
Status | In Review [ 10002 ] | Stalled [ 10000 ] |
Status | Stalled [ 10000 ] | In Testing [ 10301 ] |
Assignee | Sergei Petrunia [ psergey ] | Elena Stepanova [ elenst ] |
Link |
This issue causes |
Assignee | Elena Stepanova [ elenst ] | Oleg Smirnov [ JIRAUSER50405 ] |
Status | In Testing [ 10301 ] | Stalled [ 10000 ] |
Status | Stalled [ 10000 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | In Testing [ 10301 ] |
Assignee | Oleg Smirnov [ JIRAUSER50405 ] | Elena Stepanova [ elenst ] |
Link |
This issue is part of |
Assignee | Elena Stepanova [ elenst ] | Ramesh Sivaraman [ JIRAUSER48189 ] |
Assignee | Ramesh Sivaraman [ JIRAUSER48189 ] | Oleg Smirnov [ JIRAUSER50405 ] |
Status | In Testing [ 10301 ] | Stalled [ 10000 ] |
Fix Version/s | 10.11.0 [ 28411 ] | |
Fix Version/s | 10.11 [ 27614 ] | |
Resolution | Fixed [ 1 ] | |
Status | Stalled [ 10000 ] | Closed [ 6 ] |
Link |
This issue causes |
Labels | CONNECTOR_RELATED | CONNECTOR_RELATED Preview_10.11 |
Zendesk Related Tickets | 164352 150968 150559 |