Share via

XTP_THREAD_POOL- lot of spids running in background when no sql workload is there.

Sreeni G 1 Reputation point
2021-07-09T04:26:29.84+00:00

In our L&P systems, before the actual run kickoffs we have a SOP to run rebuild indices and update statistics job. Recently we are seeing SQL memory consumption is great than 80 % even after the above jobs get completed and there is no SQL workload running behind the scenes.

When we do sp_who2 and run some diagnostic queries to see the current activity we mostly see spids related to XTP_THREAD_POOL (with wait type -DISPATCHER_QUEUE_SEMAPHORE -its count is 53,in our db we have three in-memory tables).

We didn't observe this behavior in our previous runs, can someone please explain what SQL is consuming high memory and not releasing it and why this behavior not seen previously. (we take system utilization for our every run ,we are doing this type of load testing from past few years)

Note : In few msdn links few MVPs mentioned this behavior is normal but wanted to know if anything related to in-memory tables causing this or any other factors, please share your thoughts.

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
14,494 questions
Transact-SQL
Transact-SQL
A Microsoft extension to the ANSI SQL language that includes procedural programming, local variables, and various support functions.
4,705 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. CathyJi-MSFT 22,376 Reputation points Microsoft External Staff
    2021-07-09T08:31:09.433+00:00

    Hi @SreeniG-7743,

    Quote from the old thread What are all the XTP_THREAD_POOL processes doing

    113259-screenshot-2021-07-09-163146.jpg

    If the response is helpful, please click "Accept Answer" and upvote it, as this could help other community members looking for similar queries.

Your answer