64p vs 32p September 07, 2005
Reviewer: Gabriel Paulovic from Toronto, Canada
How a single number makes the difference ...
IBM eServer p5 595 64p
IBM eServer p5 595 32p
.... besides, we run applications not TCP-C tests here ... :-)
Followup:
yes, I wonder how many people have read the tpc-c spec and it's somewhat
artificial constraints. It is an interesting 7 table or so benchmark (including
things like gap free sequence numbers!)
首先,32位和64位的差别是巨大的;其次,要求连续的ID对ORACLE是不公平的,这将会导致本来可并行操作的事务变成串行(实际应用中,ORACLE推荐用SEQUENCE产生ID,但无法保证其连续性)
it is interesting to download the full disclosures and see what they did in the
physical implementation as well.
Reviewer: Gabriel Paulovic from Toronto, Canada
How a single number makes the difference ...
IBM eServer p5 595 64p
IBM eServer p5 595 32p
.... besides, we run applications not TCP-C tests here ... :-)
Followup:
yes, I wonder how many people have read the tpc-c spec and it's somewhat
artificial constraints. It is an interesting 7 table or so benchmark (including
things like gap free sequence numbers!)
首先,32位和64位的差别是巨大的;其次,要求连续的ID对ORACLE是不公平的,这将会导致本来可并行操作的事务变成串行(实际应用中,ORACLE推荐用SEQUENCE产生ID,但无法保证其连续性)
it is interesting to download the full disclosures and see what they did in the
physical implementation as well.