Home/ Questions/Q 350567
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T11:33:43+00:00

Here are my basic assumptions: Wcf executes my service operation methods on IOCP threads

  • 0

Here are my basic assumptions:

  1. Wcf executes my service operation methods on IOCP threads (UnsafeQueueNativeOverlapped) instead of normal ThreadPool threads (QueueUserWorkItem).

  2. Blocking I/O should not be done inside of one-way service operation methods.

  3. Blocking I/O should not be done inside of a normal ThreadPool thread.

I believe that the best strategy is to chain async calls. So, if I receive a message into my one-way service operation, I then do an async call to my db and when that completes, do my next async db call, etc. and finally respond via my wcf callback…

However, it’s hard to do every single database call async. I have resorted to breaking rules 2 and 3 above, but I don’t like it because I believe this will starve the ThreadPool eventually. Are there any better strategies?

I have looked into using Jon Skeet’s CustomThreadPool, but I’m not sure if that’s the answer either.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I would suggest breaking rule 3 by queuing up synchronous I/O calls for the ThreadPool to perform. The service methods still return immediately, but the work gets done in the background eventually, perhaps kicking off a return notification.

    • 0