Performance regression for insertion with PK.

[finnschiermer]

We have a performance regression for inserting objects with a primary key. The regression was introduced with Core v6.

It is visible for commits which are relatively small compared to the table being updated.

For commits about 10% of table size there is no problem. For commits of 1% of table size there is often a problem.
The performance drop continues to increase with smaller commit sizes relative to the overall table size.

It is already the case, that writing data using few larger commits are generally faster than many smaller commits,
but this regression impacts smaller commits beyond what was the case prior to Core v6.

The regression is most pronounced for string primary keys, but may also hit integer primary keys, depending on the insertion pattern.

[finnschiermer]

We will fix this.

In some cases it is possible to work around the problem by using an indexed property instead of setting a primary key.

[meismyles]

I believe this issue is affecting us when updating - having to remain on an old version for now. Any idea on a timeframe to resolve?

[sync-by-unito]

➤ Finn Andersen commented:

Qualified guess: A few weeks from now.

[sync-by-unito]

➤ Finn Andersen commented:

Should be fixed by Core v11.0.0-beta.6