Profile migrate UI batch request

Created on 10 May 2016, over 8 years ago
Updated 14 July 2023, over 1 year ago

Problem/Motivation

#2694391: Separate cache bin for migrations β†’ removed some of the discovery caching for migrations to speed up development.

While this should be negligible for migrations run via drush, we don't know the impact on migrations run via the UI.

In general, the performance of migrate batch requests is worth looking at in general - we might find migrate performance issues here that are harder to see via drush - and given the number of requests made per migration a hundred milliseconds could add up to several seconds or minutes by the time the migration is done.

Proposed resolution

Run a migration from 6-8 and profile the migrate batch request with xhprof or similar.

Remaining tasks

User interface changes

API changes

Data model changes

πŸ“Œ Task
Status

Closed: outdated

Version

11.0 πŸ”₯

Component
MigrationΒ  β†’

Last updated about 13 hours ago

Created by

πŸ‡¬πŸ‡§United Kingdom catch

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States mikelutz Michigan, USA

    Closing this as there has been no activity in years and no indication that the discovery caching has been problematic.

Production build 0.71.5 2024