List:General Discussion« Previous MessageNext Message »
From:Leonardo Francalanci Date:June 21 2004 5:37pm
Subject:R: R: why CPU is high while disks are idle in a table scan???
View as plain text  
> Oh.  You didn't say thta. :-)

Well, I wrote
" Doing a simple "SELECT SUM(MYFIELD) FROM MYTABLE" I noticed "
but don't worry ;)


> How much RAM does your machine have?  If it's nearly all cached,
> you'll be CPU bound rather than disk bound.

1Gb.

I'm using Solaris 8.

The SUM() works as expected now (disks works a lot), but accessing by key
is very cpu-intense and still 0% work on disk.

To sum up: table scans are very disk-intense (which make sense), accessing
by
key leaves disk on idle (I see that it should not work as with a table scan,
but at least a little!)

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