Hi,
Using nopCommerce v3.80 and nopAccelerate
Our store is having over 100,000 categories at the moment, we plan to go live with about 1,000,000 and couple million products as part of the migration from our old eCommerce to nopCommerce.
The method CatalogController.PrepareCategorySimpleModels() as we see in v3.80/3.90 loads all the categories and build the recursively the hierarchy, making the website startup very long, and timing out the ASP.NET.
What would be the optimization in the CatalogController.cs to avoid this problem?
Thanks for the help.
+100,000 categories
Certified Developer
- 274
- 1987
- 3/1/2009
- Bulgaria
[email protected] wrote:
A few things you need to think about, at least, there are a few things i would consider here. First, you need to follow the code to understand what its doing. Its loading localized data, languages, its getting the urls for the categories, its getting the number of products in the categories...basically its doing a lot. Also, its caching the results. So how much memory is that going to use. Not mention serialization (in and out of cache).
If it was me, i would build that model once and store it, say in a lucene index, ravendb or a simple text file.
Hi,
Using nopCommerce v3.80 and nopAccelerate
Our store is having over 100,000 categories at the moment, we plan to go live with about 1,000,000 and couple million products as part of the migration from our old eCommerce to nopCommerce.
The method CatalogController.PrepareCategorySimpleModels() as we see in v3.80/3.90 loads all the categories and build the recursively the hierarchy, making the website startup very long, and timing out the ASP.NET.
What would be the optimization in the CatalogController.cs to avoid this problem?
Thanks for the help.
Using nopCommerce v3.80 and nopAccelerate
Our store is having over 100,000 categories at the moment, we plan to go live with about 1,000,000 and couple million products as part of the migration from our old eCommerce to nopCommerce.
The method CatalogController.PrepareCategorySimpleModels() as we see in v3.80/3.90 loads all the categories and build the recursively the hierarchy, making the website startup very long, and timing out the ASP.NET.
What would be the optimization in the CatalogController.cs to avoid this problem?
Thanks for the help.
A few things you need to think about, at least, there are a few things i would consider here. First, you need to follow the code to understand what its doing. Its loading localized data, languages, its getting the urls for the categories, its getting the number of products in the categories...basically its doing a lot. Also, its caching the results. So how much memory is that going to use. Not mention serialization (in and out of cache).
If it was me, i would build that model once and store it, say in a lucene index, ravendb or a simple text file.
- 6
- 40
- 9/13/2017
- United States
seanrock wrote:
Ok thanks seanrock, my primary concern was if an existing solution was around. We think to store the model in Redis or Solr later
Hi,
Using nopCommerce v3.80 and nopAccelerate
Our store is having over 100,000 categories at the moment, we plan to go live with about 1,000,000 and couple million products as part of the migration from our old eCommerce to nopCommerce.
The method CatalogController.PrepareCategorySimpleModels() as we see in v3.80/3.90 loads all the categories and build the recursively the hierarchy, making the website startup very long, and timing out the ASP.NET.
What would be the optimization in the CatalogController.cs to avoid this problem?
Thanks for the help.
A few things you need to think about, at least, there are a few things i would consider here. First, you need to follow the code to understand what its doing. Its loading localized data, languages, its getting the urls for the categories, its getting the number of products in the categories...basically its doing a lot. Also, its caching the results. So how much memory is that going to use. Not mention serialization (in and out of cache).
If it was me, i would build that model once and store it, say in a lucene index, ravendb or a simple text file.
Using nopCommerce v3.80 and nopAccelerate
Our store is having over 100,000 categories at the moment, we plan to go live with about 1,000,000 and couple million products as part of the migration from our old eCommerce to nopCommerce.
The method CatalogController.PrepareCategorySimpleModels() as we see in v3.80/3.90 loads all the categories and build the recursively the hierarchy, making the website startup very long, and timing out the ASP.NET.
What would be the optimization in the CatalogController.cs to avoid this problem?
Thanks for the help.
A few things you need to think about, at least, there are a few things i would consider here. First, you need to follow the code to understand what its doing. Its loading localized data, languages, its getting the urls for the categories, its getting the number of products in the categories...basically its doing a lot. Also, its caching the results. So how much memory is that going to use. Not mention serialization (in and out of cache).
If it was me, i would build that model once and store it, say in a lucene index, ravendb or a simple text file.
Ok thanks seanrock, my primary concern was if an existing solution was around. We think to store the model in Redis or Solr later