Have a webshop with about 600 finalized orders in, and im seeing an order xml file of 8.4 mb. and when we hit the backend after an apprecycle it will timeout(guessing its because its rebuilding it or something).
Im in the process of making a lock on this file for a version 2. In version 3 the file is deleted. Would it be an idea to remove this file from v2 as well and people will have to make custom sql if they need advanced data?
First of all i guess i cannot reduce this file in any way right ? as of the current solution i am talking about ? And that it sometimes regenerates the full file.
On the thought of v2 and advanced data what are you thinking here ?
Its the search method that uses paged sql so it should be pretty quick. Have you done something custom code that searches in a different way? We have shops with 10000+ orders which run fine.
Nothing at all. I have other shops running aswell with x000 of orders but its on 1.x.
Its running on an Azure SQL, so should be okay.
The customer called this morning and timed it to 6 min(i upped the executing timeout) on the request before it failed in the message.
Only thing that is special is that im in the shop overview(this is what she opens when it takes along time) and in the overview im pulling 2 order properties.
Seeing massive order xml cache for 600 orders
Hey :)
Have a webshop with about 600 finalized orders in, and im seeing an order xml file of 8.4 mb. and when we hit the backend after an apprecycle it will timeout(guessing its because its rebuilding it or something).
Is there anyway to reduce this ?
its running tc 2.3.2.
Im in the process of making a lock on this file for a version 2. In version 3 the file is deleted. Would it be an idea to remove this file from v2 as well and people will have to make custom sql if they need advanced data?
Kind regards
Anders
Hey :)
First of all i guess i cannot reduce this file in any way right ? as of the current solution i am talking about ? And that it sometimes regenerates the full file.
On the thought of v2 and advanced data what are you thinking here ?
Can you send a stack trace of what happens when you get the timeout?
Of course you can :)
Another quick question, in TC 2.x is there a method to get all finalized orders as orders and not XML :)
Even local im getting this when i have a decent amount of orders.
Do you have a slow SQL? :)
Its the search method that uses paged sql so it should be pretty quick. Have you done something custom code that searches in a different way? We have shops with 10000+ orders which run fine.
Kind regards
Anders
Nothing at all. I have other shops running aswell with x000 of orders but its on 1.x.
Its running on an Azure SQL, so should be okay.
The customer called this morning and timed it to 6 min(i upped the executing timeout) on the request before it failed in the message.
Only thing that is special is that im in the shop overview(this is what she opens when it takes along time) and in the overview im pulling 2 order properties.
its a tc 2.3.2 and umbraco 6.1.6
Could you try and not pull those 2 properties and see if that helps? Do you have custom cs file or just the view that is custom?
is working on a reply...