PDT ConfigCheck - SQL001 SQL Query Test - FAILED

Hello,

I’m running the PDT Config Check against my E10.1.600.16 database and I’m getting a FAIL on the SQL001 - SQL Query Test.

(First of all, a warning that this line item doesn’t seem to highlight in RED like the others so it was hard to see at first.)

This is the message I’m getting…(no laughing please :blush: I probably have some serious performance tuning to do)

[4,195.0] milliseconds taken to finish SQL Query test. During the test the loop executed [1000] times. Each iteration of loop had 2 SQL read queries. Time <= 3500ms PASS, Time >= 4000ms FAIL, else WARNING.

I’ve looked in the PDT Help and Performance Tuning Guide and EpicCare and E10Help.com but I can’t seem to find anything that points me towards the things I need to fix/adjust/modify to get this test (and I’m assuming ultimately my server and E10.1) to perform faster. This server is Virtualized with VMWare if that matters for this test.

Thank you for any help and guidance you can provide!
-Heather :slight_smile:

Some of the best guidance comes from the PDT itself. Have you cleared up any other failed tests such as the SQL Setup Check? If so, are you running a split environment with the application server and database server being different virtual guests? If split, are the servers on the same physical host and hopefully the same subnet? Are you running the latest PDT (2.6.753.xxx)?

1 Like
  1. Make sure every other SQL check in the PDT has a PASS status.
  2. Make sure the physical host’s C-states are disabled in the BIOS.
3 Likes

I have one or two outstanding failed tests that I’m working on clearing up. I have both the database and application server on the same virtual. I notice that I am not running the latest version of the PDT and will get that downloaded. Once I clear up those other failed items I’ll run my configcheck again and report my findings. Thank you for the suggestions @danbedwards!

I do have a couple of outstanding Failed items in my configcheck list that I need to clean up and will work on that today. :blush: And I will double-check my physical host’s C-states to make sure they are disabled in the BIOS! Thank you so much @aidacra! :slight_smile:

Having C-States on killed me.
When I disabled them, it dropped the time from 11,000ms down to 3,000ms!

2 Likes