Just as a heads, we’ve run into some performance problems on with Coreapps server with a relatively large database of 250,000 patients at our hospital in Haiti. The patient search had become quite slow (up to 30 seconds or so), and, additionally, was slowing down the system overall, and spiking the CPU load up to 30 during our busiest periods.
One thing we figured might be a problem is the “autosearch” functionality when typing in a patient’s name–ie, when a user types in a name, whenever there is a 500ms delay between keystrokes it runs a search. We figured this could be a big performance hog that had little benefit, so we disabled this functionality by simply settting the coreapps.searchDelayShort and coreapps.searchDelayLong global properties to very high values (ie 999999999), which essentially means an end user needs to hit Enter to trigger a search.
We noticed drastic performance improvements from the system has a whole after making this change, so would recommend it for any implementations for large databases. Also, I’d suggest that we made the “autosearch” and “opt in” feature by setting the default values of the searchDelay global properties to high values?
Take care, Mark