BBCRM (hosted) Recurring Gift Processing Through BBMS - 140 Transactions per Minute

When running the credit card process in BBMS for a recurring gift batch with 44,000 rows, we have a processing time of about 140 transactions per minute. This includes the BBMS processing plus writing the results back to the batch. The process seems slow to complete. We would appreciate hearing about processing time from other clients who are hosted and use BBMS for recurring gift processing.

Additionally, we almost always get a timeout before the completion of writing results to the batch. The timeout happens after 2 to 3 hours of processing and we are able to resume afterwards.

Comments

  • @Vicki Goodwin
    We only get about 20-50 records per minute, using the ‘Credit card processing process’ in BBCRM, which is using BBMS. That's from go to whoa, so generating the payments, processing them through BBMS, and updating the batch. We have much smaller volumes than you, though; only a few thousand records at a time.

    Kind regards,

    David Wanless, The Wilderness Society.

  • @David Wanless

    Thanks for the response with what you experience while processing credit card batches. We would love to hear if any other clients experience the timeout we do when processing a large credit card batch.

  • @Vicki Goodwin at UNC-Chapel Hill, we run about 1400 recurring gift transactions each month on the 15th. The last run took about 40 minutes, but looking at my process history, it varies pretty widely. April took only 11 minutes, and February only 3 minutes!… but January, March, May, June, and July all took 38-40 minutes.

  • @Rick Root
    Thanks for the comparison info. We need for our process to not time out but maybe the number of transactions per minute isn't too bad.

  • @Rick Root
    A related question, how long does it take for your credit card batch to commit?

  • @Vicki Goodwin One thing you could do is split the recurring gift batch into smaller batches. I did a customization to do this with some of our other batches. The customization is just a record op (built for a specific type of batch template) that creates new batches and then moves a specified number of records to thew new batch, and then repeats until the original batch has less than the specified number of records in it.

    Basically something like this within a while loop:

    UPDATE top(@NUMROWS) BATCHREVENUE SET BATCHID=@TARGETBATCHID WHERE BATCHID=@SOURCEBATCHID




  • @Vicki Goodwin There are also a variety of timeout settings in the BBCRM web.config file. Likely you're a hosted client so you don't have access to it, and I don't know if any of those settings would help, but that would be a question for BB Support.

  • @Rick Root
    That reminds me, a few years ago we did have Blackbaud change the timeout setting because we decided we would rather time out than for the process to get hung up on something and just sit for a long time.

  • @Rick Root

    Thanks for the idea. The size of the batch doesn't significantly reduce the time to commit when we tried a batch half the size. I suspect it is the process of applying the recurring gift payment that is eating up the time. We might need a solution from Blackbaud to speed up the process if that's possible.