modelar7

I have the same problem with transients.
Within three days the wp_options table had grown to over 12GB. The original size of the entire database was about 650MB. We have over 8700 products on the site. Including variants, it is about 18,500 products.
I did not make any updates to WP, WC, theme or plugins. The size of the wp_options table started to grow for practically no reason. I restored the website from a backup from a time when the database was a good size and its size started to grow again. New regulars in wp_options are still being added and the size of the database is growing.
I copied the entire website including the database to another domain. The database size is the same and new rows are not added. It only happens on the main domain.
I have disabled all plugins except woocommerce and rank math and activated the base theme. The number of rows in the wp_options table keeps increasing.
I am attaching a link to a screenshot from the DB: https://ibb.co/8gQxqWc
I have set the default row display in the database table to 25 rows per page.
On the test domain, the wp_options table has 1570 pages, and from time to time about 6 rows are added, which gradually disappear.
On the main domain, the wp_options table has 2065 pages, and their number is constantly increasing.
I can even go to page 2267, but all of them up to page 2065 are empty. But it is gradually filling up, and by the time I finished writing this post, there are already new rows on page 2067 and they are still increasing…
I tried deleting transients through wp and also through a plugin, their number did not decrease.
According to the hosting where my site is located, the following are the numbers of accesses to the site by Google bot and Byte Speeder:
Google bot
Yesterday 15,000 times
Sunday 5,600 times
Saturday 6,000 times
Friday 5,900 times
Thursday 4,200 times
Byte Speeder
Today 1,700 times
Monday 4,600 times
Sunday 4,700 times
Saturday 6,200 times
Friday 3,800 times
Could this be caused by bots? Or is the site’s security broken? It really only happens on the main domain, and a website with a database copied without any changes to the backup domain does not have this error.

WP: 6.7.1
WC: 9.6.0
PHP: 8.3.14
DB: Maria DB 11.4.3
Theme: Woodmart