List:General Discussion« Previous MessageNext Message »
From:Leonardo Francalanci Date:June 21 2004 5:10pm
Subject:R: why CPU is high while disks are idle in a table scan???
View as plain text  
> Hard to say, but in a table scan the CPU does have a lot of work to
> do.  It needs to do about 16,000,000 comparisons (based on your info).

Why comparison? It's a sum...
And the table is not small: 272,000,000 bytes!

And disk is very low (almost 0%)
Thread
• why CPU is high while disks are idle in a table scan???Leonardo Francalanci21 Jun
  • Re: why CPU is high while disks are idle in a table scan???Jeremy Zawodny21 Jun
    • R: why CPU is high while disks are idle in a table scan???Leonardo Francalanci21 Jun
      • Re: R: why CPU is high while disks are idle in a table scan???Jeremy Zawodny21 Jun
        • R: R: why CPU is high while disks are idle in a table scan???Leonardo Francalanci21 Jun
          • Re: R: R: why CPU is high while disks are idle in a table scan???Jeremy Zawodny21 Jun
  • Re: why CPU is high while disks are idle in a table scan???Brent Baisley21 Jun
    • R: why CPU is high while disks are idle in a table scan???Leonardo Francalanci21 Jun
• Re: R: why CPU is high while disks are idle in a table scan???SGreen21 Jun
  • R: R: why CPU is high while disks are idle in a table scan???Leonardo Francalanci22 Jun
• Re: R: R: why CPU is high while disks are idle in a table scan???SGreen22 Jun
  • R: R: R: why CPU is high while disks are idle in a table scan???Leonardo Francalanci22 Jun