August 25, 2011 at 11:24 am
Can anyone shed some more light on the EXECSYNC wait type? I've seen it appear in WAITSTATS on other systems that use parallelism, but it's usually pretty far down on the list (with CXPACKET on top). But I've migrated my database to a very beefy SQL 2008 R2 box and I'm seeing slower performance with long EXECSYNC waits on large queries. I've done some googling, but there doesn't appear to be much out there.
For reference, the new system is, as I said, SQL 2008 R2, running on Windows 2008 R2 64-bit. The server is an IBM System x3850 X5 with 40 logical processors (2 10-core) and 128GB of RAM. And the backend is a new EMC VNX 5700. I've run update stats on the entire database with fullscan, so query plans should be optimal. MAXDOP is set to 10.
On paper, this server should fly, but it's slower than the same database running on a virtual server with 8 processors, 32GB memory, and our old SAN. Something's not adding up.
Thoughts?
August 25, 2011 at 11:35 am
That's the definition I can get from MS, not sure if it actually helps.
Occurs during parallel queries while synchronizing in query processor in areas not related to the exchange iterator. Examples of such area are bitmaps, large binary objects (BLOBs) and the spool iterator. LOBs can frequently use this wait state. Bitmap and spool use should not cause contention.
August 25, 2011 at 11:43 am
Thanks. I saw that, but it didn't really clarify anything for me. 🙂
We're not using LOBs in this database. Can you explain what, exactly, that first sentence means?
August 25, 2011 at 11:45 am
Colleen M. Morrow (8/25/2011)
Thanks. I saw that, but it didn't really clarify anything for me. 🙂We're not using LOBs in this database. Can you explain what, exactly, that first sentence means?
Nope, you need Paul White or another internals expert for that one.
May 1, 2014 at 9:36 pm
For example, this happens when you start a import/export wizard to copy data to a table. it starts two process, one process selects the data and other one inserts the data. This is parallel query/process.
When you stop and exit your import/export wizard for some reason, the insert(bulk insert) goes away, but the parallel query select does not go away, which you can see using sp_who2 command.
This process will take its own time to go away, but if you kill this select process deliberately, then the EXECSYNC happens.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply