I was wondering if anyone has any advice or "tales from the dark side" about changing the AutoCommitInterval property of the ITransactionsOptions interface? It's the sort of thing I generally leave well alone!
I am developing some code that populates dictionaries with a lot of information. The dictionary key is an integer and the item is an ArrayList with potentially several thousand entries and I can have many thousands of key/item entries in my dictionary. Ultimately I want to write the lot to a File Geodatabase Table. I was hitting the out of memory exception so a solution was to periodically write the contents of the dictionary to the table, clear out the dictionary and continue in my loop. This works but the process of writing the dictionary data to the table is quite slow (as it's writing millions of rows) and I was looking for ways to improve performance.
My code is using an insert cursor with row buffering and I believe that section of code is as optimal as I can get it, so I was looking at the best practice page on the ESRI website when I picked up on the idea of changing the Auto Commit Interval. I've never tinkered around with that before and I was wondering if people had any advice, it looks like I can set that to zero and do the commit right at the end, is this advisable, does it actually improve write performance?