vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Jonathan Lewis wrote: > The difference is only likely to be a couple of > percent of CPU at max. > > > I don't have a convenient one at hand, but it's > easy to build. Something like the following > should do. > > 9.2, LMT, not ASSM > > The values in-line are for the example in a > 2K blocksize tablespace, the values after > the -- are for a16K blocksize tablespace. > > Just check the block dumps to make sure > that the 'colliding values' have actually hit > the same block as the other id=1 rows. > > create cluster c1 ( > hash_col number(10) > ) > single table > hashkeys 15 -- 101 > size 128 > hash is hash_col > tablespace test_2k -- test_16k > ; > > create table t1 ( > id number(10) not null, > descr varchar2(80) > ) > cluster c1(id) > ; > > insert into t1 > select rownum, rpad('x',80) > from all_objects where rownum <= 14 -- 100 > ; > > insert into t1 values (1,'Colliding value'); > > commit; > > rem check CPU usage > > declare > v varchar2 > begin > for i in 1..1000 loop > select descr into v from t1 where id = 2; > end loop; > end; > / > > rem check CPU usage Thanks. -- Daniel Morgan http://www.outreach.washington.edu/e...ad/oad_crs.asp http://www.outreach.washington.edu/e...oa/aoa_crs.asp damorgan@x.washington.edu (replace 'x' with a 'u' to reply) |