SQL Browser memory management problem on machine with more than 32 logical processors

We have seen recently that on machines which has more than 32 logical processors sometimes SQL browser stops responding and only way to bring SQL Browser into proper state is to restart browser service.

When such scenario happens we have seen that SQL Browser memory consumption increases to almost 1.9 GB and after that it just stays there. (Compared to usual 10-20 MB memory consumption)

Now 1.9 GB is all that SQL Browser can use as it is 32 bit process.

So once it reaches that mark it will not have any flexibility to process new incoming requests.

Question comes why memory consumption increases to 1.9 GB at all at first point.

While troubleshooting we figures out that it is some sort of memory management problem where SQL Browser do not release memory and as a result in keeps on staggering till it reaches 1.9 GB.

Only good way to avoid this condition is to set affinity for SQL Browser service to less than 32 processors.

Usually affinity to 8 processor works fine as SQL Browser is not very heavy on CPU generally.

We have seen this problem with SQL 2012 (including machines with only SSAS 2012) and SQL 2008 r2 as well.

So this ends here…. Small and Sweet J

Let me know if you have any questions for me...