I have been using the commerce kickstart install profile and amending it to my needs. I find it useful to maintain a rebuild path during development and have used your install profile as a template successfully.

There is one stage of install that has been bugging and that is migration. The migrations just seem to take so much longer as an install task rather compared to running the same migrations in migrate_ui. I have been doing tests rebuilding a site just migrating 59 taxonomy terms into one vocabulary. This is just one migrate class. It took 200 seconds as an install task and 2 seconds in migrate_ui.

I am telling you this because I thought my findings could be useful to you since you have been involved in doing the migration on install for commerce kickstart. I found that if I used a different approach and used a form install task and declared the migrate batch operations in the submit function for the form then I could get the same speeds for migration as I was getting in migrate_ui. I then declare a callback function to run on completion of migration and then I redirect to the relevant stage in the install process.

Comments

jsacksick’s picture

Why don't you send a patch ?

nlisgo’s picture

OK, I will do when I get a moment. I'll create for the dev version. But it's just as a suggestion. Your needs are different to mine as well because your install profile is being exposed to a lot of people whereas mine is just ikos internal. :)

bojanz’s picture

Would like to see that.
We also have the pending change in https://code.drupalcommerce.org/#/c/463/ which tries to rewrite the function, and could also affect the speed.

lsolesen’s picture

Issue summary: View changes

@bojanz It seems that the pending change should be handled somehow?

bojanz’s picture

Status: Active » Closed (duplicate)