Mikhail
It was caused by an endless loop in the page's codes that is triggered
only under certain conditions.
On 5/11/2016 4:07 PM, Mikhail Khludnev wrote:
On Wed, May 11, 2016 at 10:16 AM, Derek Poh wrote:
Hi Erick
Yes we have identified and fixed the page slow
On Wed, May 11, 2016 at 10:16 AM, Derek Poh wrote:
> Hi Erick
>
> Yes we have identified and fixed the page slow loading.
>
Derek,
Can you elaborate more? What did you fix?
>
> I was wondering if there are any best practices when it comes to deciding
> to create a
Hi Erick
Yes we have identified and fixed the page slow loading.
I was wondering if there are any best practices when it comes to
deciding to create a single collection that stores all information in it
or create multiple sub collections. I understand now itdepends on the
use-case.
My
Not quite sure where you are at with this. It sounds
like your slow loading is fixed and was a coding
issue on your part, that happens to us all.
bq: Is it advisable to has as less number of
queries to solr in a page?
Of course it is advisable to have as few Solr queries
executed to display a
Hi Erick
In my case, by denormalizing,that means putting the product and supplier
information into one collection?
The supplier information arestored but not indexed in thecollection.
We haveidentified itwas a combination of a loop and bad source data that
caused an endless loop under
Denormalizing the data is usually the first thing to try. That's
certainly the preferred option if it doesn't bloat the index
unacceptably.
But my real question is what have you done to try to figure out _why_
it's slow? Do you have some loop
like
for (each found document)
extract all the
Hi
We have a "product" collection and a "supplier" collection.
The "product" collection contains products information and "supplier"
collection contains the product's suppliers information.
We have a subsidiary page that query on "product" collection for the
search. The display result include