RMS HQ Client/HQ Server Performance Issues @ Synchronization

Nov 21, 2006 3 Replies
O

Hi,



We have an issue with performance of RMS HQ client/HQ server. A simple style



51 SQL update statement according to HQ client log can take up to 5 minutes to process. I cant for the life of me understand why?

We have over 40 RMS (v 1.2.0171) Store ops client installations each PC runs Windows XP SP2 and has a P4 3.0ghz + 1 Gb RAM and has a SATA RAID. Each client/store has a 512/512 SHDSL connection back to our HQ server.



Our HQ server is a dual processor running Windows 2003 Server + SQL Server Enterprise Edition and has 9GB of RAM with fibre to a SAN with RAID sets dedicated to individual databases.



So our hardware should barely be ticking over when the RMS synchonization process occurs. But it doesnt. HQ server frequently freezes and the it once took 12 hours for one HQ Client/Store to process 152 worksheets. Due to this process completing so slowly, more and more clients bank up trying to connect to HQ server and it kills the processor.



Does anyone know how the so called 'smart algorithms' in RMS synchronization work? Anybody got any ideas as to why it is so slow or how to speed it up?



Thanks in Advance



Vote
Twitter Facebook LinkedIn
O

Thanks for the advice Mike,

Will have to look at culling some more data maybe. We already archive purchase orders from our HQ database. Currently our HQ database is to 13.3 Gb.

Did some analysis today and it seems that HQ server is fighting with SQL for both processors maxing them out as more and more clients connect. It also seems HQ server can't feed the clients requests fast enough so is getting bogged down and slowing down the whole process.

Might be time to buy some more CPUs, but you wouldnt th> I've had similar problems. The one thing that seems to have the biggest

Vote
Twitter Facebook LinkedIn
C

Thanks for the advice Mike,

Will have to look at culling some more data maybe. We already archive purchase orders from our HQ database. Currently our HQ database is to 13.3 Gb.

Did some analysis today and it seems that HQ server is fighting with SQL for both processors maxing them out as more and more clients connect. It also seems HQ server can't feed the clients requests fast enough so is getting bogged down and slowing down the whole process.

Might be time to buy some more CPUs, but you wouldnt think such a simple application could hog an entire Xeon 2.2Ghz processor. Obviously it can.

"Mike" wrote:

Vote
Twitter Facebook LinkedIn

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required