Performance of raw vs cooked partitions

I have just conducted some performance test on an HP I-70 machine running Oracle version 7.0.15.4. The tests were conducted to guage the performance of raw and cooked partitions. The tests ran multiple large queries aginst tables in the same tablespace. Using the HP performance tools I saw that INODE and CACHE wait states caused the jobs running under cooked to be slower. Under raw these INODE and CACHE wait states went away and the jobs seemed to run much smoother. The question I have is what INODE entry was causing the INODE wait states. Is it the INODE associated with the tablespace .dbf file, or is it the INODE associated with the .dbf for the database. If anyone can answer these questions or has any further information on this subject please send me mail. Thanks.

Bill Robinson					Champion Products
champion_at_rock.concert.net			It takes a little more