X-Cart forums

[aim]

Originally Posted by Sembroidery

On a store updated from older versions some (a few) tables show InnoDB while others are MyISAM. Would it be recommended to switch all tables to InnoDB?

Hello,

It is definitely recommended in 3 cases.

1) You are using the newest MySQL/MariaDB version.

or
2) You are experiencing the loss of productivity due to the Meltdown Fix.
https://forums.mysql.com/read.php?21,664350,664350#msg-664350

or
3) You are experiencing the MySQL error 'MySQL table is marked as crashed and should be repaired'
https://confluence.atlassian.com/confkb/mysql-table-is-marked-as-crashed-and-should-be-repaired-151519802.html

In other cases, it is recommended to measure the BEFORE/AFTER performance on a dev server.

Thank you.

[Sembroidery]

For the past few days we're experiencing periodical site outages. Host support staff claim the reason most probably was very high bot activity with bots hitting the site and tying up MySQL queries.
As one of the measures they suggest switching from MyISAM to InnoDB.

Are there any changes in 4.7.10 as compared to 4.7.9 that would cause issues if x-cart is subjected to high bot activity?

[aim]

Originally Posted by Sembroidery

For the past few days we're experiencing periodical site outages. Host support staff claim the reason most probably was very high bot activity with bots hitting the site and tying up MySQL queries.
As one of the measures they suggest switching from MyISAM to InnoDB.

Are there any changes in 4.7.10 as compared to 4.7.9 that would cause issues if x-cart is subjected to high bot activity?

Maybe your SEO position has been improved due to some of these changes.

[*] 25 Sep 2018, aim - Improvement (Y:148652): [SEO] Google PageSpeed Insights improvement. CSS Delivery Optimization. Prioritization of visible content. Reduction in the size of the above-the-fold content.
[*] 23 Jul 2018, aim - Improvement (Y:148676, Y:148675): Optimization for product's widgets like New Arrivals/Bestsellers/Upselling products and so on. [SEO] Google PageSpeed Insights improvement.
[*] 03 Jul 2018, aim - Improvement (Y:148675, Y:148676): [Advanced_Customer_Reviews] Huge optimization for customer reviews menu. [SEO] Google PageSpeed Insights improvement.
[*] 22 Mar 2018, aim - Improvement (Y:148619): [SEO] Google PageSpeed Insights improvement. Added minification for CSS + JavaScript resources.[ Minify Resources]
[*] 22 Aug 2018, aim - Improvement (Y:148687, B:0049702): Cookies are now secure and satisfy the PCI Compliance requirement. Only for stores with configured HTTPS. Thanks to Joe Funderburg (Cherie). https://help.x-cart.com/index.php?title=X-Cart:Configuring_HTTPS

It seems you are in the green zone
there
https://developers.google.com/speed/pagespeed/insights/

Could you ask your hosting for the bot's HTTP_USER_AGENT?
Maybe our XCRobots::getRobotsSignatures() method has to be corrected.
It should help to reduce the amount of MySQL queries.


Thank you.

[Dougrun]

I'v been having sql errors ever since this update. Today i was locked out of admin after a xcart_sessions_data sql error. Repairing the tables fixed it.



Not sure if it matters but its a InnoDB table. Most of my tables are MyISAM. I'm running 10.2.18-MariaDB



It should be noted that I also updated to the latest MariaDB just before the update

[Sembroidery]

Originally Posted by aim

Maybe your SEO position has been improved due to some of these changes.


It seems you are in the green zone
there
https://developers.google.com/speed/pagespeed/insights/

Could you ask your hosting for the bot's HTTP_USER_AGENT?
Maybe our XCRobots::getRobotsSignatures() method has to be corrected.
It should help to reduce the amount of MySQL queries.


Thank you.

Google page speed insight results have in fact improved drastically both for mobile and desktop. Thanks for that!

The most heavily active bots for the past few days were MJ12bot (200K+ hits & 4.8+ gigs), Semrushbot, Baidu, and some others. There are a couple of Unknown bots as well.

[Dougrun]

Originally Posted by aim

Hello,

It is definitely recommended in 3 cases.

1) You are using the newest MySQL/MariaDB version.

or
2) You are experiencing the loss of productivity due to the Meltdown Fix.
https://forums.mysql.com/read.php?21,664350,664350#msg-664350

or
3) You are experiencing the MySQL error 'MySQL table is marked as crashed and should be repaired'
https://confluence.atlassian.com/confkb/mysql-table-is-marked-as-crashed-and-should-be-repaired-151519802.html

In other cases, it is recommended to measure the BEFORE/AFTER performance on a dev server.

Thank you.

is it safe to run

ALTER TABLE table_name ENGINE=InnoDB;

on a live shop (assuming I close the shop)

[cherie]

Originally Posted by Dougrun

is it safe to run

ALTER TABLE table_name ENGINE=InnoDB;

on a live shop (assuming I close the shop)

Yep, that looks right. Just make sure the table is backed up first.

Here is more info on InnoDB: https://dev.mysql.com/doc/refman/5.5/en/innodb-introduction.html

[aim]

Originally Posted by Dougrun

I'v been having sql errors ever since this update. Today i was locked out of admin after a xcart_sessions_data sql error. Repairing the tables fixed it.

Not sure if it matters but its a InnoDB table. Most of my tables are MyISAM. I'm running 10.2.18-MariaDB

It should be noted that I also updated to the latest MariaDB just before the update

Originally Posted by Sembroidery

Google page speed insight results have in fact improved drastically both for mobile and desktop. Thanks for that!

The most heavily active bots for the past few days were MJ12bot (200K+ hits & 4.8+ gigs), Semrushbot, Baidu, and some others. There are a couple of Unknown bots as well.

Hello,

I have uploaded a patch to update the bot signatures.

It will prevent xcart_sessions_data table overload.

Thank you.

[Sembroidery]

Thank you very much for the patch!

Originally Posted by aim

Hello,

It is definitely recommended in 3 cases.

1) You are using the newest MySQL/MariaDB version.

or
2) You are experiencing the loss of productivity due to the Meltdown Fix.
https://forums.mysql.com/read.php?21,664350,664350#msg-664350

or
3) You are experiencing the MySQL error 'MySQL table is marked as crashed and should be repaired'
https://confluence.atlassian.com/confkb/mysql-table-is-marked-as-crashed-and-should-be-repaired-151519802.html

In other cases, it is recommended to measure the BEFORE/AFTER performance on a dev server.

Thank you.

The MySQL version is 5.5.61-cll. Host support did not report problems as per 2) and 3). I don't think that we can do dev server testing, because in order to have realistic results to compare, we'll have to duplicate our site on the Internet which does not sound like a good idea to me.

We could eventually switch our site to use an InnoDB copy of the database for a while to see what happens. Wonder would it be wise to do it?

[aim]

Originally Posted by Sembroidery

The MySQL version is 5.5.61-cll. Host support did not report problems as per 2) and 3). I don't think that we can do dev server testing, because in order to have realistic results to compare, we'll have to duplicate our site on the Internet which does not sound like a good idea to me.


We could eventually switch our site to use an InnoDB copy of the database for a while to see what happens. Wonder would it be wise to do it?

InnoDB in MySQL 5.5 has some limitations which have to be checked by technical staff.
https://stackoverflow.com/questions/15678406/when-to-use-myisam-and-innodb
https://dba.stackexchange.com/questions/22678/when-to-switch-from-myisam-to-innodb

Please contact our support staff at https://secure.x-cart.com/ - I'm not sure if this is something that can be solved via a forum discussion, unfortunately.

Thank you.