•  

Announcement

Announcement Module
Collapse
No announcement yet.

cout(*) a Perf Killer?

Page Title Module
Move Remove Collapse
Conversation Detail Module
Collapse
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts

  • cout(*) a Perf Killer?

    #1
    Hi I just want to aks whether you all can
    confirm, that count(*)s from big tables are performance killers?!

    I think so because a simple access by primary key takes virtually no time, while a count(*) takes 300ms.

    thanks
    Tags: None

  • #2
    They are instant on myiasm tables, but slower on innodb.

    http://dev.mysql.com/doc/refman/5.0/en/innodb-restrictions.h tml

    Comment


    • #3
      Most count(*) performs a range scan on an index.

      The only specific case when this is not done is the MyISAM special case when you select count(*) of the entire table. And that is because MyISAM keeps the total nr of rows in the table as meta data for the table.

      Best way to keep the time short is to make sure that you have enough RAM and allowing enough memory for caching. That way this index range scan will be performed entirely in RAM which usually is fast enough for most needs.

      Comment

      Working...
      X