Categories
View Replies (4)

Resolved Google Shopping Export Advice For Large Product Files

  1. batetim
    batetim
  2. RO CSVI
  3. Friday, 24 February 2017
  4.  Subscribe via email
Morning

Running Joomla! 3.6.5 VirtueMart 3.0.18.2

Currently updating csvi from 5.21.2 to CSVI Pro 7.0.2

We have for some time used csvi 5.21.2 export for our google merchant centre feed.

On the new csvi i have successfully set up the export template but am finding the export is much slower than the previous version and is limited to a max of about 1500 lines before server timeout (takes about 38 mins). We have about 15000 products and ideally i would prefer not to have 10 seperate export templates to run each time to make 15000. With csvi 5.21.2 we found we could extract about 4000 products at a time and much quicker.

Can you lend any advice to how we can speed up/improve export process?

I notice it pulls it as one large file, but i wondered if it was possible to break up the export much like on the import you can specify:
Lines per import
Time between imports

I have attached a log file of the 1500 lines which i can successfully export but takes some time to run for your info com_csvi.log.19.zip

Kind regards

Tim
0
Responses (4)
tharuna
tharuna
Accepted Answer Pending Moderation
Hello Tim,
Yes, you need to replace ey6v4 with your table prefix so the table can be identified.
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
batetim
batetim
Accepted Answer Pending Moderation
Hi Tharuna

Have added table to database and loaded patch, but getting eror message:

Error
Table '2016DBD-lk-u-025832.#__csvi_sefurls' doesn't exist SQL=SELECT COUNT(`sefurl_id`) FROM `#__csvi_sefurls` when exporting

From the previous article Roland had advised following to create new table:

CREATE TABLE IF NOT EXISTS `ey6v4_csvi_sefurls` (
`sefurl_id` INT(11) UNSIGNED NOT NULL AUTO_INCREMENT,
`plainurl` VARCHAR(255) NOT NULL,
`sefurl` VARCHAR(255) NOT NULL,
PRIMARY KEY (`sefurl_id`),
INDEX `plainurl` (`plainurl`)
) CHARSET=utf8 COMMENT='Stores cached SEF URLs for export';

Should we replace ey6v4 with our own database prefix - apologies my database knowledge is not that great!

Kind regards

Tim
  1. more than a month ago
  2. RO CSVI
  3. # 2
batetim
batetim
Accepted Answer Pending Moderation
thats perfect thanks Tharuna we will try this

Kind regards

Tim
  1. more than a month ago
  2. RO CSVI
  3. # 3
tharuna
tharuna
Accepted Answer Pending Moderation
Hello Tim,
There was a change done in CSVI 7 in generating SEF URLs which has made exports to run slower. What actually happens is the CSVI makes a call to the front-end to generate the actual SEF URL because front end is where Joomla generates proper SEF URLs. This process takes time that in turn affects the export. To solve this issue we have introduced cache for SEF generation. This issue has been discussed and the patch for cache is in the thread here. This improvement will also be coming in our next CSVI version. You can follow the instructions to apply the patch file in the thread and then run the export.
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. # 4
  • Page :
  • 1


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