Hi Bob,
I'm not certain, but I suspect something else is responsible for the delay. I ran some tests with > 20,000 calls, > 400 contacts, > 6000 unique phone numbers and > 1000 phone numbers for one contact, and the difference between that and a nearly empty database was negligible. (I measured the time between call reception and running the action.)
It could be that you're using phone number patterns heavily or something else in the database that I haven't considered. However, the slowness you're experiencing could be because of logging, debug messages, or a slow computer due to many other programs.
If you're using a debug version of Ascendis Caller ID, try using version 2.3.0.0:
http://ascendis.com/callerid/CallerID_Setup.exe
If your actions log to the activity log or access other files, try disabling that part of the actions. Recent versions of Ascendis Caller ID log every time an action is run (which means for each call), so if your disk is full or slow, that could be a factor. Of course, database access on a slow or failing disk could also cause the behavior you're seeing.
If that doesn't help, check Windows' Task Manager to see how much physical (not virtual) memory is available and check CPU load. If those numbers show plenty of real memory and CPU time available, consider backing up your database, clearing it (by restoring the empty database included in the program folder), and testing. When done testing, restore your database.
Finally, consider sending a backup of your database to me (at support at ascendis dot com) so I can run some tests here.
Finest regards,
Bill Root
Ascendis Software LLC