iMIS esereies - handling transaction volume spikes

 

I know this is a broad question, may have many answers, may not be an iMIS problem (but infrastructure) and is probably only related to this customer, but thought I would ask in case anyone had a similar scenario and how they handled.
 
The customer is running iMIS 15.1.3, uses eseries 15.1.3 for web and has a custom CC provider. The site runs properly processing eseries and CC transactions for events and dues. There are two times a year when there is a spike in volume when 100’s of people want to register for a specific series of events at once when the events are opened at noon. As one indictor, we saw on Coldfusion 200+ connections shortly after noon. The login and registrations are slow, there are some timeouts, and we have found reconciliation discrepancies between the CC provider and iMIS CC transactions – there were probably timeouts after checkout and CC processing and before the iMIS table inserts/updates for the registration.
 
We are exploring a number of options, that include business and technology, and are considering a load/capacity planning exercise.
 
If anyone has had scenarios like the above and information on how to handle, we would appreciate any comments, guidelines or solutions you implemented. I am hoping there are some specific iMIS/eseries performance tuning tips that can prevent a major load/capacity project

Thanks Nick