Temporary tables as engine = MEMORY ?

[MyZeD]

Summary (*)

How we all know is the magento 2 shopsystem not the fastest on the market. Every minutes is running the index or something else and creates, renames, drop temporary tables. This is not an overkill, but use to capacity the HDD/SSD.

Examples (*)

CREATE TABLE IF NOT EXISTS catalogsearch_fulltext_scope2 [...] CREATE TABLE IF NOT EXISTS catalogsearch_fulltext_scope5 [...] INSERT INTO catalog_category_product_index_store2_replica [...] TRUNCATE TABLE catalog_category_product_index_store1_replica [...] ALTER TABLE catalog_category_flat_store_11 RENAME TO catalog_category_flat_store_11_old [...]

Proposed solution

Would it help, to create this tables directly as Memory-Tables as Engine ? This would be a makes all faster and more weight-light. If the Server or Database crashes - after this the PHP-Script doesn't do anything with it and let it as trash back in the database.

What do you think about it ?

[m2-assistant[bot]]

Hi @MyZeD. Thank you for your report. To help us process this issue please make sure that you provided the following information:

• [ ] Summary of the issue
• [ ] Information on your environment
• [ ] Steps to reproduce
• [ ] Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@MyZeD do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• [ ] yes
• [ ] no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant[bot]]

Hi @engcom-Echo. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

@engcom-Echo Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• [ ] Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again. Thanks!

[magento-engcom-team]

:white_check_mark: Confirmed by @engcom-Echo Thank you for verifying the issue. Based on the provided information internal tickets MC-29683 were created

Issue Available: @engcom-Echo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[sdzhepa]

Hello @MyZeD

Thank you for your feedback and your proposal!

Based on the description and label feature request the issue has been transferred to Magento Feature Request public repo.

Additionally, based on Issue reporting guidelines feel free to raise this topic on the next resources:

Before creating an issue, please do the following: ...

• Make sure, that information you are about to report is a technical issue, please refer to the Community Forums or Magento Stack Exchange for technical questions, feature requests, etc. These reports are not guaranteed to be processed within GitHub issue tracker.

[m2-assistant[bot]]

Hi @MyZeD. Thank you for your report. To help us process this issue please make sure that you provided sufficient information.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[woutersamaey]

The MEMORY storage engine is not supported on a MySQL if GTID is enabled. So in my opinion, this feature should only be used if MySQL is configured not to use GTID. This can be dynamically queried.