Just wondered what everyone has this set to? Default is Cleanup Orders Older Than 7 days and run every 24 hours.

Currently I am looking to change it to older than 2 days and run every 24 hours. Does anyone leave it for a long / shorter period?

from a site performance has anyone seen an issue with running it every 24 hours VS say 72 hours? I have never checked my logs but it would be interesting if google crawls around the same time a cart cleanup happens. Im sure if it runs every day there would be an overlap quite often.

Kim thanks for the heads, up, Aaron, we are not suffering from that issue however currently we do have far more carts than I am comfortable seeing retained. Thank you for the feedback.

Preface: BV treats a 'cart' as an unplaced order.

BV's cart cleanup process performs a search for all unplaced orders that fall within the cleanup time period. This search returns the complete row of data for each order, which is unnecessary to perform a delete. The reason that data is being returned at all rather than simply performing the cleanup inside a stored procedure is because there is some business logic, like returning inventory to stock, that must be run while performing an order delete (side note: there actually is a stored procedure to perform a cart cleanup solely from the database, but you can't run it without first closing the store).

The above will work just fine so long as you don't have too many carts to clean up. With larger stores, and/or when keeping carts for a longer period of time, this becomes a problem (and especially if you are creating a cart on every visit to the site like the TekGear theme does). Before a single order is deleted the system must load every order it is going to delete into memory. If the number of carts to delete is large, this process can timeout (and therefore never delete a single order), cause the app pool to recycle (which stops the cleanup process and also causes your website to restart), or suck up all of the server's memory bringing performance to its knees.

The big improvement with our cleanup process is that it simply returns the ID (bvin) value of the orders that must be deleted. This is the only piece of data you need to perform a delete. This search is much faster and consumes a fraction of the server memory because we're only storing a 36 character value for each order. We also made the delete process a little more efficient when you're not tracking inventory. Also, the cleanup process logs the number of carts found and the number cleaned up to BV's audit log so you have a better idea of what's going on.