Performance during import for assigned media asset
Sometimes customer may face the case that more items(or products/variants) with assigned media asset are desired in system, or some exiting items should be enhanced with more assigned media assets. All such cases can be simply covered with a import job. But with the time the corresponding import job will be performed more and more slowly, the more media assets are assigned to an item, a next import for assigning further media assets to the same item takes more time. It is due to that fact that the item object is more and more complex after be assigned with more and more media assets, so that it takes more time for saving detail model by each import action. It can not be avoided since its current structure design, but the total performance can be improved with a parallel solution if it is possible. For that customer should check his hardware and adjust the import file according to the corresponding hot folder setting.
Hardware: the customer system should be enhanced with a better hardware(more CPUs), so that it can support the multi-thread solution.
Hotfolder setting
if the import job is scheduled per hotfolder whose configuration is NOT under any constraint of hotfolder group, then all import files will be performed in parallel.
if the import job is scheduled per hotfolder whose configuration is under constraint of hotfolder group, and the import files will be performed consecutively. In this case the import performance can be improved like following:
combine more items in each import file, so that multi threads can be actually used to process the different items in parallel for each import file. During the processing for each import file, it is firstly analysed how many different items are included in the import file. This number will be used with the plugin_customization.ini setting "importer.maxThreads"(if this setting is not set, then the available processor will be analysed) together to calculate the actual threads which perform the import works. E.g.
Item number in import file
defined "importer.maxThreads" value
Result: actually scheduled threads for import
2 items(each with several media asset assignments)
4
2
4 items(each with several media asset assignments)
2
2
That means, all assignments for the same item inside one import file will be performed in one thread. That is just the reason that the import file contains only one item(for different media asset assignments) can not be improved even if the "importer.maxThreads" is set with more threads.
set a accommodating value for the setting "com.heiler.ppm.importer5.core/importer.maxThreads" in the plugin_customization.ini file at the server side. If it is not set, then it will be set by default as twice the number of cores.
On the other hand, a corresponding story HPM-41919 - As an user I want to import assigned media asset to item with a stabilized performance. Open is also created for this problem and will be planned in the future.