[Idea] List of performance issues on PrestaShop software that are worth investigating

[matthieu-rolland]

The problem

This is a copy/retranscription of a slack discussion about performance issues worth investigating in the PrestaShop software.

• translations page: it seems it rescans translations every time you search for a new phrase, even if you made a typo, see discussion here

• stock manager performance with a lot of order: "See more" / "See less" links in the "Module manager" tab #28116, @kpodemski tested one of the community PRs and it works correctly, what we’d need to do is making it cleaner. It drastically improves performance of creating an order (last step in PaymentModule::validateOrder) and managing the stock in BO (issue) We know mid-sized merchants use ERPs, but this also impacts perf of front office as mentioned

• more products in shopping cart: we know it’s a real pain for everyone working with PrestaShop, insightful discussion here: Cart / Checkout performance issue for multiple products in basket #14979 - watch out: this is not only about CartPresenter, this is about the Cart::getProducts method as well, and the problem we have by doing three-level querying of products sometimes, query from Cart::getProducts, then Product::getProductProperties, then we “present” the results, and we perform even more queries, one more product in cart is approx. 300-400 queries more sometimes - this is something what could make a great marketing material if fixed - one more hint: it is worth browsing phrase “slow cart” and “cart performance” even for closed issues because we mark them as duplicate and some of the helpful insights are almost lost (example here)

• autoupgrade module scans entire shop to create xml file to determine what to upgrade, etc., this causes a few minutes loading time of upgrade screen (Infinite load when opening autoupgrade module #30913 issue not reproduced but I’m sure it’s there because I’ve had it myself) - solution is to stop scanning some of the directories like /img/p

• PrestaShopLogger, possible quick-win: PrestaShopLogger can cause performance impacts in FO as many module developers use it incorrectly and log actions in front office, then if you have millions of records in logger it is causing visible performance problem if addLog method is called (more details and possible solutions: PrestashopLogger isPresent doesn't work and performance lack #27887)

• Generation of pdf invoice: when selected from date to date, it can be way too long when there are many invoices
  is having max execution time issues with 400 invoices.
  Possible solution: generation per batch (let's say 10 by 10) in several ajax queries, with a progression bar in the UI, so that there's no max execution time issues and the user sees what's happening. @elyesnaouar also thinks that SQL queries can be improved on this.

The solution

Investigate and fix if possible;

Alternatives

No response

Additional context

No response

Do you plan to work on this subject?

• I'm willing to contribute a formal specification.
• I'm willing to provide any wireframes or design assets required for this feature.
• I'm willing to submit a Pull Request that implements this feature.
• I'm willing to help verify that the implemented feature works as intended and produces no unintended side effects.

[matks]

#35978 just got posted 😄

[matks]

Some interesting links #19689 and #19701

[matks]

Check this out #36004 (comment)