Fast Asynchronous Re-indexing 1.1.9

Frequently Asked Questions

  1. What Processing Mode should I use: Per Entity or Per Index?

    Per Entity mode process reindex queue per product, while Per Index mode process queue per products index.
    For more information about Processing Modes, check the General Settings page

  2. When i use the Processing Mode - Each Index, does it do a full reindex, or only indexes changes?

    Each Index reindex only changes too (all changes for first index, for second index etc)

  3. What Processing Mode makes reindex faster?

    Per Index mode works faster, but it less reliable, because it requires more memory for executing.
    As a result, there is a possibility of reaching memory limits and locking the reindex process.

  4. What is a purpose of the Force process queue button?

    Force process queue allows to make reindex via web browser.
    If after clicking the button reindex doesn't start, it means that reindex currently executing by cron.

  5. How to test the extension works correctly or not?

    Go to System > Index Management. Click the button Detail Log and check the lines with the State status Error.
    Other statuses indicate that the extension works correctly.

  6. What is the relationship between the time of reindexing, the product amount, the number of store view, server performance?

    Time of reindexing depends on the number of products and storeviews. The more of them exist, the more time need to make reindex.
    Server capacity also effects on the time of reindex process.

  7. How to know what is the most appropriate value for "Max queue batch size for processing" option?

    This variable depends on your server capacity. Recomended value for slower servers is 100 and for fast servers < 1000.
    You can set the approximate value and check if the reindex was succesfully finished.
    If reindex process wasn't executed, you can reduce value untill it fits your server configuration.

  8. How to set up extension for various import schemes?

    • Default import mechanism.
      Doesn't require additional settings.
    • Import through Magmi
      Extension settings Validate Product Index and Validate Category Index must be enabled for successfull import.
    • Import through a user script
      Before importing script, you need to disable Asynchronous full reindex option at General Settings.
      After script was imported, make native magento reindex via SSH (command of native magento reindex described at Command Line Interface page).

  9. What is the difference between Full Reindex and Reindex for changes?

    Full Reindex performs reindex of all products, while Reindex for changes makes reindex of only changed products.
    Usually, you should reindex only changed products and perform full reindex only in critical situations.

  10. Does Full reindex can run through default mechanism of Magento, but run reindex of the changed products via extension?

    Yes, you can set up such conditions. Go to System > Configuration > Mirasvit Extensions > Fast Asynchronous Re-indexing.
    Set No for the Asynchronous full reindex and set Yes for Asynchronous reindex for changes option.

  11. When I run indexing through asynchronous reindex why CPU load is high?

    The same CPU load you can see when you run reindex without our extension.
    Extension improve time of reindex by moving all reindex tasks to cron.

  12. In which cases should be used "Clear the queue" button?

    This option can be used when some problems are appeared with extension work.
    For example, when a lot of products were added to reindex queue and extension can't handle with such amount of products.
    Another possible reason, when extension makes reindex more slowly then before.

  13. What steps should i do to clear the queue successfully?

    Follow next steps:

Fast Asynchronous Re-indexing