Archiving extremly slow after Update 4.1.1 -> 4.2

Support & Bugs
1

After an Update to 4.2 archiving has become extremly slow, even when using auto-archive with a cronjob:
/usr/bin/php /path/to/matomo/console core:archive --url=http://example.org/matomo/

mytop shows that temporary tables are created and dropped very slowly and the archiving does produce high server load. All this came with the update to 4.2 and was not a problem before.

On that server Matomo is running on PHP 7.3 and MariaDB 10.0.38.

Thx,
Flux24

2

Same thing for me after upgrading.

My DB now shows extremely slow requests:

# Query_time: 14.090704 Lock_time: 0.000408 Rows_sent: 27 Rows_examined: 832177 Rows_affected: 0
...
# Query_time: 13.458145 Lock_time: 0.000383 Rows_sent: 27 Rows_examined: 832177 Rows_affected: 0
...
# Query_time: 18.084339 Lock_time: 0.000351 Rows_sent: 27 Rows_examined: 832177 Rows_affected: 0
...

I will try to downgrade to 4.1.x

3

I confirm performances are much better with Matomo 4.1.x

4

Same Problem here. Upgraded directly from 3.x so I cannot tell wether 4.x below 4.2 works better for me, but 4.2 is so much slower than my previous version that it is hardly usable anymore. Php Version is 7.3 aswell.