10-20-2014 06:58 PM
OnBase 13 SP2
We have our Application Server on a virtual server. In an attempt to improve performance, we reconfigured the virtual machine from a single processor to dual processor. Instead of improving performance, the opposite has occured. For example, queries now take TWICE as long to return the hit list.
While I'm waiting for help from my support, can anyone give me any ideas of why performance got worse? Any ideas of what I should check?
It's been a bad day.........
Thanks for any suggestions.
-Deborah
10-21-2014 11:22 AM
Matthew - Thanks for the great information. One additional point for my understanding, you stated you keep the Application Server at one core, what about the SQL and web servers. Is that a recommendation or best practice on those VMs also?
We did note a significant degredation in performance this last time we upgraded to OB V12 and moved our SQL Server to Win2012, HyperV. Our SE team, of course is denying it is related to the VM (we were on a dedicated server prior to upgrade) and so we are living with less than optimal performance. I'm wondering if # of cores on the SQL and Web (ArchiveLink and BIC integration on these servers also) is having a detrimental effect.
Thanks so much! L 🙂
10-21-2014 11:49 AM
I think it's recommended to keep your SQL server on a dedicated physical server, not a VM. At least that's always what we've been told (and I think it's reflected in the OnBase documentation as well, somewhere).
10-21-2014 01:19 PM
10-22-2014 02:27 PM
Also look at Parallellism in SQL
10-23-2014 05:44 AM
Thank you all for the great information. I'm going back to my DBA team and having a serious discussion! L 🙂
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.