Re: Deadlock Detection in InnoDB storage engine
Hi Aftab/Rick,
Thanks for all the support we got.
We finally migrated from GUID to INTEGERS as our primary key using built in AUTO_INCREMENT feature with InnoDB Engine as default storage Engine.
We also moved from GUID to INTEGERS for WHO columns in our application.
I am very glad to update few of the performance improvement seen in our application.(4 compute units 7.5 GB ram)
We ran the test both on GUID and INT as Primary Keys for 15K records.
1. Database storage size reduced to nearly 400%.
2. We have Batch Billing module which improved 700%.
3. Creating the accounts I/O operations improved by nearly 400%.
I would like to thank again for the support from the forum.
Regards,
Manjunath.
Subject
Views
Written By
Posted
6457
July 24, 2012 06:03AM
1944
July 24, 2012 09:49AM
1639
July 24, 2012 10:10AM
1550
July 24, 2012 10:24PM
1482
July 25, 2012 02:38AM
1305
July 25, 2012 04:59AM
1271
July 25, 2012 05:04AM
1249
July 25, 2012 05:19AM
1271
July 25, 2012 11:39PM
1373
July 26, 2012 02:32AM
1330
July 26, 2012 06:33AM
1237
July 27, 2012 10:30PM
1462
July 31, 2012 12:00AM
1647
July 31, 2012 02:32AM
1171
July 31, 2012 05:10AM
4510
August 01, 2012 12:03AM
1302
August 01, 2012 06:05AM
1188
August 02, 2012 03:20AM
Re: Deadlock Detection in InnoDB storage engine
1105
August 28, 2012 06:28AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.