Poorly written assembly and CLR

Poorly written assembly and CLR

• reddeagle

  Adam,
  On point 1 is it true that SQL OS punishes threads/assemblies that are performing poorly How does this happen On what criteria does SQL OS decide this
  
  On Point 2 I agree with you.
  
  Thanks
  

• Fil Mackay

  Most of the memory for CLR comes outside SQL Server buffer pool. If the system runs out of memory then your CLR routine would get an OOM exception and SQL Server would abort this thread and consequently the memory would be freed.
  
  For CPU, yes SQL Server punishes the threads that do not yield the scheduler in a reasonable amount of time. It would force them to yield and put them at the end of the scheduler.
  
  Thanks,
  -Vineet.

  
  
  

• Hadez

  1. Whether it will affect the overall performance of the server depends on whether or not the server has enough memory and resources to handle however much it is chewing up :)

   

  2. Yes, other assemblies in the same AppDomain could be affected; but you can control this to some degree by splitting things up into different AppDomains by using different owners...

   

  But let's get down to the more important question:  If this assembly is so badly written, and using so much memory, why are you hosting it in-process   Wouldn't this be a better candidate for the application tier   The situation you describe is really no different than a badly written or improperly implemented T-SQL stored procedure.  If you have something eating up all of the RAM and processor time on your server, perhaps you need to take a hard look at it from an architectural point of view.

   

  
  --
  Adam Machanic
  Pro SQL Server 2005, available now
  http://www..apress.com/book/bookDisplay.html bID=457
  --

   

   

  <Yedu@discussions.microsoft..com> wrote in message news:79d20459-8f1e-435f-97d9-9c8423852d11@discussions.microsoft.com...

  As the CLR is hosted in the SQL OS.

  How will the SQL OS handle a situation wherein I have a badly written .net assembly which is chewing up lot of memory and other system resources of the server.

  1. Won't it directly affect the SQL OS and the overall performance of the server

  2. The bad assembly is also hosted in the same app domain as other assemblies;As all assemblies owned by same user are hosted in the same app domain; will this approach not affect other .net assemblies running in the same Appdomain
  
  Thanks!

  
  
• Poorly written assembly and CLR