Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: wp-cli/search-replace-command
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v2.0.20
Choose a base ref
...
head repository: wp-cli/search-replace-command
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v2.1.0
Choose a head ref
  • 8 commits
  • 2 files changed
  • 2 contributors

Commits on May 10, 2023

  1. Configuration menu
    Copy the full SHA
    cbfbaf7 View commit details
    Browse the repository at this point in the history
  2. Use single test that works for all tested PHP versions

    Co-authored-by: Alain Schlesser <alain.schlesser@gmail.com>
    brandonpayton and schlessera authored May 10, 2023
    Configuration menu
    Copy the full SHA
    b1671b5 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    536a527 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    5c54825 View commit details
    Browse the repository at this point in the history
  5. Make PHP replacement more efficient

    This change makes PHP replacement queries and memory usage more
    efficient.
    
    It improves the primary key SELECT queries by eliminating the use of
    OFFSET because OFFSET requires that the database consider all rows up to
    OFFSET before taking rows up to the LIMIT. The new query relies on
    primary key conditions to more efficiently eliminate previous rows from
    consideration. This way, the database can use an index to identify rows
    with keys greater than those of the previous chunk.
    
    It improves memory usage by doing updates along the way rather than
    storing all a column's updates in memory until the end. At Automattic,
    when we limit search-replace to 4GB of memory, we sometimes exceed that
    limit for large sites. It's possible there are other things that
    contribute to high memory usage within the search-replace command, but
    as a first step, we can reduce memory requirements by no longer keeping
    all updated column values in memory simultaneously.
    brandonpayton committed May 10, 2023
    Configuration menu
    Copy the full SHA
    56faa0c View commit details
    Browse the repository at this point in the history

Commits on May 11, 2023

  1. Retrigger checks

    schlessera committed May 11, 2023
    Configuration menu
    Copy the full SHA
    efef299 View commit details
    Browse the repository at this point in the history
  2. Retrigger checks

    schlessera committed May 11, 2023
    Configuration menu
    Copy the full SHA
    089244d View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    c238204 View commit details
    Browse the repository at this point in the history
Loading