https://forge.joomlapolis.com/https://forge.joomlapolis.com/favicon.ico?17095821032018-01-09T20:08:01ZJoomlapolis forgeCB Activity - Bug #6973: Count query performance lowhttps://forge.joomlapolis.com/issues/6973?journal_id=176472018-01-09T20:08:01Zkrileonkrileon@joomlapolis.com
<ul><li><strong>Target version</strong> changed from <i>6.0.0</i> to <i>4.2.0</i></li></ul> CB Activity - Bug #6973: Count query performance lowhttps://forge.joomlapolis.com/issues/6973?journal_id=176482018-01-09T21:03:33Zkrileonkrileon@joomlapolis.com
<ul><li><strong>Target version</strong> changed from <i>4.2.0</i> to <i>6.0.0</i></li></ul><p>There's no improving this without changing to timestamp based paging. InnoDB doesn't optimize for count so it always has to do full table stacks. Even with simplified count query it still takes a reasonable amount of time to count against 100k+ table.</p> CB Activity - Bug #6973: Count query performance lowhttps://forge.joomlapolis.com/issues/6973?journal_id=176502018-01-10T19:30:39Zkrileonkrileon@joomlapolis.com
<ul><li><strong>Target version</strong> changed from <i>6.0.0</i> to <i>4.2.0</i></li></ul> CB Activity - Bug #6973: Count query performance lowhttps://forge.joomlapolis.com/issues/6973?journal_id=176532018-01-10T20:24:00Zkrileonkrileon@joomlapolis.com
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>30</i></li></ul><p>Seams to be a relatively easy fix by doing a "soft" count. Basically we grab the number of entries needed per page + 1 and we only grab their IDs. We then count the IDs and if grater than the page limit we know there's more than 1 page so show the MORE button. We also know if there's entries or not without having to do a full table scan for total count, which in most cases we don't even need.</p> CB Activity - Bug #6973: Count query performance lowhttps://forge.joomlapolis.com/issues/6973?journal_id=176542018-01-10T20:24:39Zkrileonkrileon@joomlapolis.com
<ul></ul><p>Implement a count_all $output for ->rows encase we do need full table count.</p> CB Activity - Bug #6973: Count query performance lowhttps://forge.joomlapolis.com/issues/6973?journal_id=176552018-01-10T22:41:46Zkrileonkrileon@joomlapolis.com
<ul><li><strong>% Done</strong> changed from <i>30</i> to <i>80</i></li></ul><p>Still need some minor optimization in the asset prefetch function.</p> CB Activity - Bug #6973: Count query performance lowhttps://forge.joomlapolis.com/issues/6973?journal_id=176582018-01-11T20:40:41Zkrileonkrileon@joomlapolis.com
<ul><li><strong>Status</strong> changed from <i>Assigned</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>80</i> to <i>100</i></li></ul><p>Asset prefetch array already included asset counts. It now can pass those on so the count query doesn't have to happen again when already prefetched. This effectively eliminates a lot of extra queries.</p> CB Activity - Bug #6973: Count query performance lowhttps://forge.joomlapolis.com/issues/6973?journal_id=176782018-01-12T21:50:22Zkrileonkrileon@joomlapolis.com
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>