René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"mariadb 11.0부터 Query Optimizer를 크게 개선","articleBody":"mariadb가 nasdaq 상장후 계속 적자를 내면서도, 개발을 꾸준히 하면서, 11부터 Query와 innodb를 크게 개선\r\n\r\nhttps://monty-says.blogspot.com/2022/12/i-want-to-wish-you-happy-new-year-with.html\r\n\r\n```\r\nYour queries are\r\n\r\nusing more than two tables\r\nusing indexes that have lot of identical values.\r\nusing ranges that cover more than 10% of a table.\r\n   WHERE key between 1 and 1000  -- Table has values 1-2000\r\nusing complex queries where not all used columns are or can be indexed.\r\nIn which case you may need to depend on selectivity to get the right plan.\r\nmixing different storage engines.\r\nLike using tables from both InnoDB and Memory in the same query.\r\nusing FORCE INDEX to force an index\r\ngetting worse (or not good enough) when using ANALYZE TABLE.\r\ndepending on --optimizer-use-condition-selectivity \u003e 1 (using selectivity to find out how many accepted rows there are in a table).\r\nusing lots of derived tables (subselects).\r\nusing ORDER BY / GROUP BY that could be resolved via indexes\r\nusing table scans when it should use keys and vice versa.\r\n```","author":{"url":"https://github.com/742soft","@type":"Person","name":"742soft"},"datePublished":"2023-12-11T14:33:05.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/102/stack/issues/102"}