• Replies 7 replies
  • Subscribers 338 subscribers
  • Views 130 views
  • Users 0 members are here
Related

LP_CUSTOMER_RANK runtime

Zach Domrese
$organization

Hello friends!

I am continuing to add to our ranking procedure and am starting to get concerned with the runtime. Currently sitting at about 60ms. I am hoping to use this thread as a little poll for how long this procedure runs for those of you that have customized it. 

I would love any tips for optimizing as well! 

I've also considered creating a nightly procedure that runs the bulk of the ranking updates and then reserving LP_CUSTOMER_RANK for incremental updates during the day. Has anyone had success with this approach?

I use this to check runtime:

DECLARE @start datetime,
		@end datetime

SET @start = GETDATE()
EXEC [LP_CUSTOMER_RANK] @customer_no=193457
SET @end = GETDATE()

SELECT @start, @end

Thanks, 

Parents
  • $organization

    We use the custom rank procedure heavily. It needs to happen with each transaction because it allows us to provide comp ticket benefits, pricing changes, and even a work-around for online "subscription exchanges". Right now my procedure run time is 313ms. I wish I could keep it shorter, but the amount of functionality we get from it has been worth the increase in processing time.

Reply
  • $organization

    We use the custom rank procedure heavily. It needs to happen with each transaction because it allows us to provide comp ticket benefits, pricing changes, and even a work-around for online "subscription exchanges". Right now my procedure run time is 313ms. I wish I could keep it shorter, but the amount of functionality we get from it has been worth the increase in processing time.

Children