Categories
View Replies (3)

Resolved Querie causes 100% CPU on server-provider

  1. mathm00
    mathm00
  2. RO CSVI
  3. Saturday, 29 December 2018
  4.  Subscribe via email
Our provider has warned us several times in the past weeks that our site was causing 6 CPU’s activity of 100% on their server. It appeared it was caused by a query from our site. We checked several things and if modules and plugins were up-to-date. No cause found. Today the provider send us more information with a process-list of the SQL query.
Here we could see that the 100% CPU problem was caused by an export product descriptions by CSVImproved. We found no error report of CSVImproved.
Our DB has approx. 2000 product records with of course multiple relations. Are there solutions to tackle this CPU problem?
As a note: We had not been using CSVImproved for several months. Only in the past weeks we did some queries again.

We use CSVImproved 7.10.0 and extensies also 7.10.0.
Joomla 3.9.1 en virtuemart 3.4.2.

Marcel
0
Responses (3)
tharuna
tharuna
Accepted Answer Pending Moderation
Hello Marcel,
I don't think exporting product description of 2000 products will cause 100% CPU usage. May i know how you decided that CSVI export query is causing this problem? Can you post the query here to check?
Kind regards,

Tharuna

=========================
If you use our extensions, please post a rating and a review at the Joomla! Extension Directory
  1. more than a month ago
  2. RO CSVI
  3. # 1
mathm00
mathm00
Accepted Answer Pending Moderation
The provider send us a overview of the process-list regarding the mysql ( see attachment marcel.txt). Looking at the query information it looks like the CSVI queries we use. Also the date and time correspond with the time that we executed the query. Only thing is that the server of the provider has 1 hour time difference ( summertime?) .
We also attach the CSVI log-file of the query where you can see the content. ( file: 1.com.csvi.oog.340.txt renamed *.php). Hope this gives you sufficient information. Otherwise please advise how to send more information.
Note: on 29th December in the section ‘CSVI-Logs’ we could see all the information including under the columm Debug log the option to show, download etc. Today (31 st. Dec) when we look, it says ‘no debug log found’. We don’t know why. On the server the log files are still there.

Kind Regards,

Marcel
Attachments (2)
1.com_csvi.log.340.txt
marcel.txt
  1. more than a month ago
  2. RO CSVI
  3. # 2
tharuna
tharuna
Accepted Answer Pending Moderation
Hello Marcel,
The provider send us a overview of the process-list regarding the mysql ( see attachment marcel.txt). Looking at the query information it looks like the CSVI queries we use. Also the date and time correspond with the time that we executed the query. Only thing is that the server of the provider has 1 hour time difference ( summertime?) .

Unfortunately the query sent in the file is not a CSVI query. We do include few of VirtueMart files in CSVI like to calculate product price but that is not possible in your case because as per your debug log you are not exporting product price fields. The actual CSVI query for exporting product description is in the debug log file you sent. You may need to check this issue with VirtueMart extension or any other extension which works based on VirtueMart.

Note: on 29th December in the section ‘CSVI-Logs’ we could see all the information including under the columm Debug log the option to show, download etc. Today (31 st. Dec) when we look, it says ‘no debug log found’. We don’t know why. On the server the log files are still there.

In your template, on Details tab check if Enable logging is set to Yes. Debug log will be generated for an import or export only when this option is set to Yes.
Kind regards,

Tharuna

=========================
If you use our extensions, please post a rating and a review at the Joomla! Extension Directory
  1. more than a month ago
  2. RO CSVI
  3. # 3
  • Page :
  • 1


There are no replies made for this post yet.
Be one of the first to reply to this post!