Usually Hybris server has a slow performance in terms of RPS due to wrong usage of coverters and populators in controllers/facades. Main wrong usecases are:
convert same Model into Data object few times populate Data object with all possible data instead of population only valuable for current page attributes To identify which populators are slow and executed more than once you can use such aspect:
OOTB hybris supports splitting of DEBMAS IDOCs by KTOKD. It means that different IDOCs can be processed with different mapping services. But in case of IDOC contains set of DEBMAS with different KTOKD values, all of them would be processed with same mapping service regardless of real KTOKD value. Unfortunately implementation of proper fix requires core changes in datahub IDOC processing, but there is an easier way to fix that issue with performance trade-off.
Hybris OOTB have a bug in getting PageModel for multicountry content catalog. Issue is located in DefaultCMSPageService.getPageForId(id) method, which executes flexible search query for all session catalogs and returns (AbstractPageModel) pages.iterator().next(). In most cases it will return root global catalog page instead of page from country specific content catalog.
OOTB hybris allows to automatically retry business process action after some time. To do this is enough to set delay in RetryLaterException and throw it. But there is no OOTB implementation of limiting amount of such retries in business processes.
One of the pretty common case in Hybris customizations is to receive master data, for example Products, from external system and use hybris only for minor changes. In such cases business wants to have flexible system, which allows to customize attribute assigning via backoffice, impex files etc.
In OOTB hybris smartedit throws FlexibleSearch errors on personalization view and most part of customization functionality doesn’t work. Exception will inform that there is an error in SQL syntax near UNION ALL.
OOTB hybris has a powerful “Flexible Search Restriction” system, which allows transparently restrict access to any hybris item type. Due to flexible search restrictions are implemented on a very low level of hybris ORM time to time unexpected issues can appear even for simple restrictions.
Adding any of SAP datahub integration extension in localextensions.xml leads to build error with root cause Extension doesn't specify a path and no scanned extension was matching the name.