Top 5 wait_stats question

I have a client that just gave me access to a new polyserve SQL environment. They have placed one production db on the server for testing after they completed setup. We gave them our requirements except for the polyserve but that was because we are not familar with the app so cannot vote for or against.

The are very secuirty aware so right now will not give access to the actual hardware so I cannot run PERFMON but was able to run a query and gather the top 5 wait stats since server startup. (4 weeks)

The SQL instance has seperate drives for data, log and tempdb 16  3ghz proc and 64GB of RAM. The OS and SQL are x64 with SQL being enterprise. With only one db on this instance the two LATCH waits concern me. What dio you guys think. I am attaching the stats and config results.

 config.rpt top5 wait stats
Robert TimmonsSenior Technical ConsultantAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Robert TimmonsSenior Technical ConsultantAuthor Commented:
I have reviewed those articles (beleieve me I have read Penal Dave complete FEB. project on wait stats! )and am aware of a few queries we have that I am going to have to add the MAXDOP hint. I am testing the new settings now and am seeing improvement in the CXPACKET wait.  Right now I am more concerned about the LATCH_EX and PAGIOLATCH_SH. This instance basically has no load with only one db in use. Should I be concerned with these? If we have disk subsystem issues I definitily do not want to start rolling production dbs into the new polyserve environment.
Daniel_PLDB Expert/ArchitectCommented:

As soon as they are low I wouldn't worry about them. Your configuration has separate physical drives for data, logs and tempdb. It is recommended optimal configuration, you can increase performance by adding more spindles to you raid config or choosing other raid config.

Occurs when a task is waiting on a latch for a buffer that is in an I/O request. The latch request is in Exclusive mode. Long waits may indicate problems with the disk subsystem.

From white paper I posted:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Robert TimmonsSenior Technical ConsultantAuthor Commented:
I agree it is not top two but is in top 5 which is not good. I am accepting this as the solution but any additional comments are welcome. I do want to say the article by Penal Dave on is a great source of info but we need all the info we can get since it is the same setup but different results depending on so mamy variables with SQL performance.

Marten RuneSQL Expert/Infrastructure ArchitectCommented:
Daniel PL is correct
You will always have waits in a SQL server. You cannot hava a empty top 5 table!
Latches will Always be set, this is a quite normal top 4, given that you take care of the CXPackets.

Regards Martenrune
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.