Review Flashcards
We have added the customer layout handle adobe_ims_login to deal with all the design changes. This handle is added via ————
\Magento\AdminAdobeIms\Plugin\AddAdobeImsLayoutHandlePlugin::afterAddDefaultHandle.
how to rebuild minified css?
where do we check if token_last_check_time was updated 10 min ago?
\Magento\AdminAdobeIms\Plugin\BackendAuthSessionPlugin
the logout event for The logout from Adobe IMS Service
controller_action_predispatch_adminhtml_auth_logout
IMS
identity management service
what is Vault ?
(stored payment information)
Magento\Variable
Allows to create custom variables and then use them in email templates or in WYSIWYG editor for editing description of system entities.
set opcache.memory_consumption to at least—– to avoid performance degradation.
2GB
For Adobe Commerce 2.3.5 and higher, update your configuration to use the extended Redis cache implementation ………
\Magento\Framework\Cache\Backend\Redis.
.magento.env.yml
stage:
deploy:
REDIS_BACKEND: ‘\Magento\Framework\Cache\Backend\Redis’
For best performance, configure a maximum of —- product options per product.
100
Manage product information through an external …..
Product Management System (PMS).
Longer response time for most storefront scenarios related to products containing—— in attributes.
many options
For Adobe Commerce version 2.3.x and 2.4.0 to 2.4.1-p1, configure no more than —– attributes
For Adobe Commerce version 2.4.2 and later, configure up to —- product attributes
500
1500
Product attribute options–Configure up to —– attribute options for each attribute
Product attribute sets–Configure a maximum of —- attribute sets
100
1000
Configuring many attribute options can affect site performance in the following ways:
Long request and rendering times on product detail (PDP) and category pages containing complex products.
Admin product save operations response time increases above optimal performance targets.
Increase in Product Edit form rendering time.
Slow checkout.
Increases in product data and index sizes can affect site performance in the following ways:
Increased response time for most storefront scenarios related to catalog browsing, search (quick and advanced), and layered navigation.
Product management operations in the Admin slow significantly which can lead to timeouts.
Product Mass Actions functionality can be blocked.
Index re-build time for mid- and large-sized catalogs cannot be performed on a daily basis due to long execution times.
Configuring many product attributes increases the product template size for each product (EAV structure) and the amount of data that must be retrieved. This increase affects operations in the following ways:
Increase in SQL queries traffic related to EAV data retrieval and the amount of data processed which results in decreased DB throughput
Significant increase in the size of Adobe Commerce indexes and the full-text search index
Reaching hard MySQL limits when building a FLAT index for oversized product templates and inability to use it
For best performance, display a maximum of —- products per page.
48
If you have more than 48 products in any category, update the storefront catalog configuration to disable the option to ———–
Allow All Products per page.
For versions 2.3.x - 2.4.2, allow a maximum of —- products in a cart.
For versions 2.4.3 and later, enhancement to sales rules capabilities increased the cart maximum to —-.
100,750
For versions 2.3.x - 2.4.2, the expected performance based on cart item limits is:
Up to — products in a cart—the product works, meeting performance targets for response time.
Up to —- products in a cart—the product works, but response time increases above targets.
Above —– products in a cart—the cart and checkout flows are not guaranteed to work
100,300,500
Use the following strategies to manage the number of cart items
Split orders into several smaller orders with a smaller number of rows by using the Add Item by SKU feature.
Only add the custom logic and cart customization required to load a list of items.
Having more than the recommended maximum number of products in the cart can affect site performance in the following ways:
Increased response time for data retrieval operations, validation of cart items, checks for applying price rules, and tax and total calculations.
Increased response time for minicart rendering including rendering of cart views, checkout flow, and execution.
Increased time loading time for all site pages where the minicart is present.