I have a site that uses Merchello 1.4ish.. I have 140k+ variants.
I'm debating moving to 2.5 but just had a couple questions!
1) Every couple months or so Merchello appears to just stop and the context is a Null reference. The only workaround is when the client tells me it's down every month or two I have to recycle the app pool and initiate a examine reindex.. Has there been any improvements in this department?
2) Searching. This was probably the most painful part of 1.x.. You could really only search by a handful of things, and searchterm has almost no documentation on it. I ended up hacking the core code manually and running raw SQL against the database bypassing the Merchello stuff. It wasn't all that important to me anyway since I was just returning JSON from UmbracoApi controller.. The SPA allows the user to filter on fields.
Example of where Merchello was simply not viable -
Search all Collections for products who's
Name contains "Heirloom" &&
Detached field "Sex" is "Male" &&
Detached field "Color" is "Red" OR Detached field "Color" is "Blue" &&
Manufacturer is Adidas
Some of these queries using the 1.x services took like 2 minutes to execute. I ended up just writing raw SQL queries but since the detached JSON is stored like key/value pairs it was just a nightmare to do any meaningful queries.
Has there been any improvement in this department? Preferably a query builder pattern, like how Examine works anyway?
That's basically it.. I'm mostly just concerned about performance, as earlier Merchello was NOT ready for this type scalable use. I see some boasts that clients have 100K+ products and life is great, but the issue is when you actually start trying to use the data.. you couldn't.
Yes I have looked at the documentation - everything looks the same, thus my question to the community.
Merchello Performance & General Questions for 2.5 +
Hey all,
I have a site that uses Merchello 1.4ish.. I have 140k+ variants.
I'm debating moving to 2.5 but just had a couple questions!
1) Every couple months or so Merchello appears to just stop and the context is a Null reference. The only workaround is when the client tells me it's down every month or two I have to recycle the app pool and initiate a examine reindex.. Has there been any improvements in this department?
2) Searching. This was probably the most painful part of 1.x.. You could really only search by a handful of things, and searchterm has almost no documentation on it. I ended up hacking the core code manually and running raw SQL against the database bypassing the Merchello stuff. It wasn't all that important to me anyway since I was just returning JSON from UmbracoApi controller.. The SPA allows the user to filter on fields.
Example of where Merchello was simply not viable -
Search all Collections for products who's
Name contains "Heirloom" &&
Detached field "Sex" is "Male" &&
Detached field "Color" is "Red" OR Detached field "Color" is "Blue" &&
Manufacturer is Adidas
Some of these queries using the 1.x services took like 2 minutes to execute. I ended up just writing raw SQL queries but since the detached JSON is stored like key/value pairs it was just a nightmare to do any meaningful queries.
Has there been any improvement in this department? Preferably a query builder pattern, like how Examine works anyway?
That's basically it.. I'm mostly just concerned about performance, as earlier Merchello was NOT ready for this type scalable use. I see some boasts that clients have 100K+ products and life is great, but the issue is when you actually start trying to use the data.. you couldn't.
Yes I have looked at the documentation - everything looks the same, thus my question to the community.
Thanks in advance!
is working on a reply...