Performance on AD_ChangeLog : some ideas

[Nicolas Micoud]

Hi,

When opening the RecordInfo panel, I sometimes have to wait for a long time (I never timed it), but I have the impression this waiting is since we migrate to v11.
Checking code and DB, I have some ideas/suggestions to improve

The where clause of the WRecordInfo panel is now

WHERE AD_Table_ID=? AND (Record_ID=? OR Record_UU=?)

(it was WHERE AD_Table_ID=? AND Record_ID=? before https://idempiere.atlassian.net/browse/IDEMPIERE-5567)


So wouldn't it be better to remove the OR and have a where clause that will be

WHERE AD_Table_ID=? AND Record_ID=?
or
WHERE AD_Table_ID=? AND Record_UU=?

according to values of Record_ID / Record_UU (I mean no need to test Record_UU if we have a Record_ID, so the OR part can be removed safely)

I also see a AD_CHANGELOG_SPEED index (AD_TABLE_ID, RECORD_ID)
Does it make sense to add a AD_CHANGELOG_SPEED_UU (AD_TABLE_ID, RECORD_UU) ?

wdyt?

Thanks,

Nicolas

[Norbert Bede]

Hi Nicolas

use table partitioning.

https://wiki.idempiere.org/en/Table_Partitioning

Norbert

[Carlos Antonio Ruiz Gomez]

Hi Nicolas, I think your suggestions make sense, please open a ticket for that and I'll take a look when possible.

Regards,

Carlos Ruiz

Am 10.06.24 um 11:09 schrieb Nicolas Micoud:

[Nicolas Micoud]

Hi Carlos

https://idempiere.atlassian.net/browse/IDEMPIERE-6169

I've added it to the TODO list, not sure when I'll be able to have a look

Nicolas