Developer forum

Hi Dmitrij,

Could you try adding the parameter Debug=True to the url? The execution table can show you where the slowdown occurs.

- Jeppe

Hi Jeppe,

Thansk for reply, this does bring very nice overview of what is going on! :)

And this immediately caught my eyes 

Other operations take miliseconds to complete.

/Dmitrij

We have not seen that behavior in our internal testing, but we have also not had 700k real products to test. You could try removing the facets and adding them one at a time to see if it's a specific facet that causes the issue. This is is unsuccessful, then we probably need the solution so we can investigate.

- Jeppe

Ok if I add/remove facet, do I need to rebuild index?

I don't think I have to, cause index is a data source, Facet is just something that uses that datasource (atleast as far as I understand).

I removed 2 major Facets, saved and closed, but no possitive effect so far.

No, it's not necessary to rebuild the index if you change your queries or facets. You got it right.

Ok, since this did not reduced the load time of that particular step not by a milisecond - I assume next step would be to wrap it up and send it to you guys?

In this case I would need to know what do I have to wrap?

As I mentioned before, this is a Custom application.

There is a DLL that we are using, that get prices from ERP, but that is pretty much it.

/Dmitrij

Are the performance issues still present if you remove your custom code?

Well than strange thing happen.

If I remove it, than yes solution becomes faster, but Facets are gone.

But I think that it becomes faster because it does not invoke any facets.

In API code there is nothing that should be on the way of facets, just plain ERP call methods, for Price provider and Order complete notification.

/Dmitrij

What is the size of your hosting environment in terms of memory? How big is your index files, take a look at /System folder and find the index there.

Ok, we are going to try adding new repository, and add one field at a time, and not use ProductIndexSchemaExtender to add fields.

Than build facets one facet at a time and see where the slow happens.

Total size of System folder is 2.61g, server has 60 GB left on Drive D and about the same on Drive C.

Total space available 80%+.

Not space, memory. Say you have 2GB of RAM, running SQL, IIS and a 2 GB index... Not good :-)

Well currency it uses only 18%, nothing suspicious.

Total size of Installed memory (RAM): 16 GB

While building index, IIS process takes 25% of CPU and 1.5 Gig RAM

/Dmitrij

Unfortunetly we are getting the same issue if we are trying to create a new index, with 4 fields, that have nothing to do with price

ProductID

GroupID 

and 2 more Custom fields

Still observing the same behaviour.

/Dmitrij

What we also noticed is variation in responsie time. Depending on what group you are slecting and how many facets are defined.

/Dmitrij

Was browsing forum for things we noticed in our solution.

And what I noticed is this:

http://developer.dynamicweb.com/forum.aspx?PID=48&ThreadID=42102

And simptoms are simmilar, Logs > eCom > Frontend > getting same error message: 

GetProductsFromIndexQuery

For some reason think they might be related.

Question:

Why Logs > eCom > Frontend > log can cause Error like this:

[2/13/2016 1:38:49 PM]:
GetProductsFromIndexQuery

Logging 'Exception':
Type: System.Collections.Generic.KeyNotFoundException
Message: The given key was not present in the dictionary.
StackTrace:    at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Dynamicweb.eCommerce.Frontend.Frontend.GetProductsFromIndexQuery()
InnerException: [null]
Data: System.Collections.ListDictionaryInternal
Source: mscorlib
Object output: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Dynamicweb.eCommerce.Frontend.Frontend.GetProductsFromIndexQuery()
------------------------------------------------------------


Logging 'URL':
http://changed.sitename.no/Default.aspx?ID=2160&Purge=True&debug=true

Hi Dmitrij

We need a link to your solution. Please create a case and send me the case number.

BR Nicolai