RSA Archer Slowness Saving the Records
We experiencing extreme slowness saving the files, it takes 20-30s to save it, this issue happens only in Production environment. When I am just trying to create a new record on a developer tool I see 401 error UNATHORIZED. I do not see any errors on application side indicating slowness, logs are not even generating when I am saving the file, the only thing that is updating is queuing service log
Thread Manager: Overall time: 0 hours, 0 minutes, 2.077 seconds
12/4/2019 9:31:02 AM - Thread Manager: Final time stamp
12/4/2019 9:31:02 AM - Packaged Message Thread 1: Shutting down.
12/4/2019 9:31:02 AM - Atomic Message Thread 1: Shutting down.
12/4/2019 9:31:03 AM - Atomic Message Thread 3: Shutting down.
12/4/2019 9:31:03 AM - Atomic Message Thread 4: Shutting down.
12/4/2019 9:31:03 AM - Atomic Message Thread 2: Shutting down.
12/4/2019 9:31:30 AM - Started Flushing index path: f:\archer_files\archer_search_index\50000\quicksearch\
12/4/2019 9:31:30 AM - Finished Flushing index path: f:\archer_files\archer_search_index\50000\quicksearch\
12/4/2019 9:36:00 AM - Started Optimizing f:\archer_files\archer_search_index\50000\quicksearch\
12/4/2019 9:36:05 AM - Finished Optimizing f:\archer_files\archer_search_index\50000\quicksearch\
Yep, that's is outlined in the, https://community.rsa.com/docs/DOC-107214 :
When planning the configuration of the Database Server, RSA recommends the following:
- Separate volumes to store SQL Server data, SQL Server Log, and TempDB components because SQL Server produces one writer thread for each physical disk. While it is preferable to also use separate spindle sets for each of these storage volumes, the separate writer thread improves performance even though these components are on the same spindle set. Note: Create completely separate disks to allow SQL servers to produce multiple threads.
- RAID10 arrays with at least separate 15K RPM spindles, solid state drives (SSD), or SSDcached drives (for example, EMC FAST Cache) for the SQL data, SQL log, and TempDB components.
Don't remember, but we have errors of communication when accessing Archer Control Panel. It was a brand new environment so we tried installing all over again and then it worked.
Stage environment works fine, but dev and stage having issues, all three environments are on different shared sql databases, which have the same configurations
Unfortunately no. Nothing has changed. You can see it below. Average time of reading incident from archer in last 12 hours is 3.2s (max: 16 689 ms - real time is more than 20 second but i am not waiting longer for the response, min:79,3 ms)
and here are the last 7 days:
The RSA Archer support saying to move our Archer to the new database which does not make any sense, CPU not going over 50% on app server or database server, we only have 20users, I do not have any idea what to do next.
I have got separate database dedicated only to Archer. 16 vCPU, 40GB RAM, SSD disk. Each database file types are now on separate volumes as it was mentioned in 6.6 documentation. Less than 0.0015% processor usage on db.