Installing the server part General information Preparing the server Launching a container Connection and installation Setting up an SSL certificate Security settings Server update
Development Environment Scripts Root scripts Modular scripts Calling a module script Module script parameters Modular script operation Web modules
Handbook Accepted designations Module data types System keys Global keys Configuration Debugging tools Service Caching Performance API Parser MySql Session Emailer IpUtil Xml
Version update

Performance

High speed is the hallmark of the Melbis Shop family of products. But it should be remembered that no matter how fast and powerful the rocket is, it must be skillfully managed and understood, and only then will it be able to unleash its full potential. Melbis Shop 6 is certainly a fast system, but we still want to give you some recommendations on how to fully utilize all its capabilities!

  • Organize your work properly.
    Formalize your store's business processes! This is a fundamental aspect that, unfortunately, is often ignored by online store owners. If you have previously worked with another CMS or system, still responsibly approach this issue, based on the peculiarities of working with Melbis Shop 6. You should not try to look for a shift knob or clutch pedal in the cockpit of a rocket. It works on a different principle. Therefore, you should pay attention to the following points:
    • There are directories whose handling requires interlocks. Explain to your employees that they can be opened in "read" mode, so that they do not block other employees from working with them. Also, assign access rights to employees in a way that minimizes such situations.
    • Working with goods is divided into two main components: non-commercial (working with the descriptive part of the goods) and commercial (working with prices, statuses, etc.). It will be right if at least two employees work with goods: a manager (creates descriptions of goods) and a logistician (monitors pricing).
    • Due to the fact that the complex Melbis Shop 6 works in batch data mode, that is, unlike the web-interface modification of tables is done in one fell swoop: make many changes to the table at once, and not "per hour by teaspoon". This is an absolute plus of the architecture of the complex is very beneficial for the caching system. After all, in this case the system will have to update the cache much less often! However, not everything depends on the system, you still need to properly organize the work. After all, if, say, type in product descriptions and click every five minutes on the button "Save", then the cache of the corresponding modules will also be rebuilt every five minutes (provided that the cache timeout is not set). Therefore, pay attention to the "Users" section where for each operation you can set the time when it can be executed! Limit the execution of certain operations during peak store hours.
    • There is a lot of potential in Melbis Shop 6, and although the system is very user friendly, you will need some time to get used to it. Similar to aviation, do not try to perform aerobatics immediately after takeoff, especially if you are an inexperienced pilot. Concentrate on the most important things, try to build a business process as simple as possible. Time will pass, and you will gradually start to use more and more functionality of Melbis Shop 6. Therefore, it is very important at the very beginning not to overload your project with elements that may be useful, but you are still not clear how to use them correctly.

  • Use the caching system.
    Caching of the work of the Shop modules is a very important component, which was detailed above (see section: Caching). It is important to use the cache correctly, in this regard we want to give you some tips:
    • Revise the modules, and increase the cache obsolescence time (timeout), it can be set individually for each module. Even a small timeout of one minute can almost double the load on your server (it all depends on the frequency of data changes, of course).
    • Develop modules in such a way that plug-in libraries have less impact on cache updates. For example, it is a bad idea to make one big library with all useful functions and connect it to all modules. As a result, changing almost any table will result in the need to rebuild each module's cache.
    • If your site is hosted on your own server, place a folder with the cache data on an SSD disk. Your hosting administrator will help you do this, it's absolutely easy. You will only need to buy an SSD disk. The thing is that the cache consists of many small files, and in this case the work of the file system itself is much faster on an SSD-disk (especially read operations).

  • Use the means of debugging modules.
    In Melbis Shop 6 there is a developed toolkit for you to quickly and clearly analyze the work of modules (see Debugging tools). Thanks to these reports, you can quickly find out which module is causing excessive delay in page loading, which SQL query is running too long or too often, etc. Remember also that MySQL DBMS has a built-in cache, which must be disabled before debugging. This is done in the "System / Installation" section, you should add the following command: SET SESSION query_cache_type = OFF

  • Add indexes if necessary.
    When developing the database architecture, we added indexes to the tables following the rule: "the less, the better". Of course, there are indexes, but only for unambiguously necessary fields. The thing is that indexes can not only speed up, but also slow down the work, especially for tables that change frequently. This is due to the fact that frequent changes of data will require frequent rebuilding of the index. For this reason, many developers add indexes only as needed, and we recommend it. That is, if you have an SQL query that takes a long time to execute, create an index on the necessary table(s), keeping in mind the frequency of changes in it(s).