Commerce Server暂存性能问题 [英] Commerce Server Staging performance's issues

问题描述

您好，

我们目前为客户提供Commerce Server Staging的性能问题。
该项目的背景是：

• 主目录包含约5万种产品。


• 有6个虚拟目录，在5000和整个目录之间的许多文章上进行了本地更改。稍后，将会有数十个虚拟目录。


• 虚拟目录在目标环境中具体化。


• 我们每天运行一个包含所有目录的增量增量（包含所有目录的1个暂存项目）。


• 它会在几分钟内生成一个大约1Gb的XML文件，但导入需要几个小时（目前约为5小时）。

假设：

• 制作多个临时项目。一个目录。


• 使用完整的临时模式而不是增量模式。


• 使用SSIS包而不是Commerce Server Staging。

您是否曾在类似的环境中遇到过Commerce Server Staging的性能问题？您还有其他可能的解决方案吗？

感谢您的帮助。
gbrout

解决方案

目录导入性能不是很好....特别是如果要发送大文件同步目录。

使用SSIS可能对性能有好处，但取决于你是什么这样做，您可能会有奇怪的数据，并且您将始终冒险使用修补程序/服务包更改数据库架构。

我建议SSIS仅更新简单数据。

我还建议您在导入数据时查看网站性能....
无论如何，您的问题的解决方案并不简单，可能您需要更详细的分析来理解为什么xml太大了等等...

Stelio 2014年>

Hello,

We currently, we have performance problems with Commerce Server Staging for a customer.
The context of the project is :

• The main catalog contains ~50 000 products.
• There are 6 virtual catalogs, with changes made locally on a number of articles between 5000 and the entire catalog. Later on, there will be dozens of virtual catalogs.
• Virtuals catalogs are materialized on the target environment.
• We run an incremental incremental containing all catalogs every day (1 staging project with all the catalogs).
• It generates an XML file of about 1Gb generated in a few minutes but the import take several hours (currently ~5h).

Hypothesis :

• Make several staging project. One by catalog.
• Use full staging mode instead of incremental.
• Use SSIS packages instead of Commerce Server Staging.

Have you ever encountered performance issues with the Commerce Server Staging in a similar environment ? Do you have any other possible solutions ?

Thanks for your help.
gbrout

 

解决方案

Catalog Import performance are not great.... specially if you are sending big files to syncronize catalogs.

using SSIS could be good for performance, but depending what you are doing, you could have weird data, and you will always risk that the database schema change with hotfix/service packs.

I would suggest SSIS only to update simple data.

I would aslo suggest to take a look at site performance when you import data....

anyway the solution of your issue is not simple, and probably you would require a more detailed analisys to understand why the xml is so big and so on...


Stelio

这篇关于Commerce Server暂存性能问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！