Question Long running query

Status
Not open for further replies.
30m rows and query time is now 0.007816. I don't think it's going to scale up to 4411 seconds by further doubling the amount of rows 😅
 
So after downgrading to MariaDB 10.3 the query takes about 40 seconds.

Truncating that table did not seem to have any adverse affect other than losing transaction history, is that correct?
 
The only thing truncating that table could affect would be if you have set any of your events to only apply every X triggers. It inserts a record with transaction_state = skipped to keep track of this.

If you don't need that feature and you don't need the history, then truncating the table should be fine.
 
Hello @Home Alone,

We hope your ticket regarding DragonByte Credits has been addressed to your satisfaction. This ticket has now been scheduled to be closed.

If your ticket has not been resolved, you can reply to this thread at any point in the next 7 days in order to reopen the ticket, afterwards this thread will be closed.

Please do not reply to this thread if your ticket has been resolved.

Thank you.


- DragonByte Technologies, Ltd.
 
Status
Not open for further replies.

DragonByte Credits

XenForo 1.5.3+ XenForo 2.0.x XenForo 2.1.x XenForo 2.2.x
Seller
DragonByte Technologies
Release date
Last update
Total downloads
4,390
Customer rating
5.00 star(s) 4 ratings
Back
Top