Support

January 22, 2018 at 11:20 am

THX. Josh,
I will start 2018 ticketing in a few weeks so have not tested the current speed, however 2017 (ending in September) was slow.
To help me take advantage of the topic discussion so far, please clarify my understanding or inferences of what has been said about Slow Speed and the wp_esp_line_item Table:

1) Current EE4.4.55p has indexes to improve Registration Checkout speed in wp_esp_line_item (LIN_code, TXN_ID). When was this change made so I can assess if it was there to influence my 2017 ticketing speed? Was it 4.4.55p?
2) Slow speed is likely related to MAL Attacks (e.g. DNoS) which propagate TXN_ID = 0 records or “Back Paging” by visitors that cause orphaned records (TXN-ID = 0) which slow down the DB Processing. I will add notice about “Back Paging” in 2018.
3) Core EE4 periodically deletes TXN_ID = 0 records, but a manual delete will be helpful if the file degrades before the automatic delete. Is the automatic delete a CRON or associated with each Update of Core? When was this delete added? Should I add my own delete Cron to run every 5 minutes?
4) My EE4 tables are all InnoDB to support use of a master-master Percona Cluster. Could this impact my Checkout Speed?
==========
In reviewing my wp_esp_line_item table, I see large orphan counts over time since there are now 21, 162 rows, auto increment = 1,225,979 and no TXN_ID = 0 rows.