optimizing the preformance of the writes is finding the right balance between the size of the batch and the number of batches that occur for an operation. if you used NH to persist 1M entities (which you really shouldn't, but that's another discussion). the preformance of executing a single statement for all 1M entities would be just as bad, if not worse than executing a single command for each of the 1M entities. Adjusting the batch size to 500, 1K, or even 20K will have a different impact on the preformance and execution time. finding that balance is a matter of trail & error, testing and experience.
On Aug 11, 5:33 am, Niclas Pehrsson <[email protected]> wrote: > What are the drawbacks of set a high number on BatchSize, why isn't > BatchSize set to the maximum per default? -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
