HQ Server Performance

We are continually troubled by performance issues in HQ.

I am about to throw more hardware at it but figured it's worth asking:

Is there anyone out there with more than 20 stores and/or more than 50K items who is not encountering performance issues with HQ? I'd like to know if you have unique SQL configurations, are running HQ server on multiple hardware instances, what works for you and what didn't. Our corp employees can wait for 10 minutes to get a query back from the server right now and often, when it's talking to the stores, it will just time out on their query.

Our server hardware is an Intel Xeon 3.0 SQL 2005 Standard raid10 with 8GB ram on Server 2003. We currently run HQ Server and SQL on the same box. We're running 2.0.0114 all locations and installations. I think that our RAID is where the current bottleneck is, they're 7200rpm SCSI drives on the Dell perc4e/di controller. When I'm watching the metrics I constantly see average disk queue length spike to 100% any time a store is connected and uploading. Yes, the database files are located on the RAID with OS and apps on a separate physical drivespace. I tried moving the tempdb back and forth to separate physical drive spaces with no observable change in performance. We have the stores connecting hourly.

I am currently configuring a new Dell Poweredge 2950 with a 6-drive SAS array and dual 2.0 Opterons. I am going to completely remove the HQ Server application from this box and will run HQ Server on a pair of workstations directly cross-connected on Gig ether to the SQL server. Is it ridiculous to have to do this or is there some trick that I'm missing?

Opinions PLEASE!

Thanks all,

Brandon

Reply to
Brandon Klassen
Loading thread data ...

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.