[Mono-list] Mono 3.1.2 on OSX, "Degraded allocations"

[Nicklas Overgaard]

Hi Rodrigo,

Thanks for the explanation.

I'm running with ServiceStack's "Long running apphost base", which
according to the documentation is using a pool of 500 threads to handle
requests:
https://github.com/ServiceStack/ServiceStack/wiki/Concurrency-model#httplistener-long-running-self-host-apphosthttplistenerlongrunningbase

I will probably take it with the authors of ServiceStack, if I can manage
to produce a test-case that reliably shows the problem.

Best regards

---
Nicklas Overgaard

Founder & Lead Developer
iSharp Solutions ApS


On Tue, Jul 23, 2013 at 2:45 PM, Rodrigo Kumpera <kumpera at gmail.com> wrote:

> Your program is causing too many objects to be pinned, you probably have
> too many threads with too big stacks.
>
> If not the case, it's a bug.
>
>
> On Tue, Jul 23, 2013 at 5:11 AM, Nicklas Overgaard <nicklas at isharp.dk>wrote:
>
>> Hi!
>>
>> I'm currently testing out the newest mono on OSX. I'm running a simple
>> ServiceStack API in a console runner, and while benchmarking a handler with
>> AB, the console suddenly contained:
>>
>> """
>> *Warning: Degraded allocation.  Consider increasing nursery-size if the
>> warning persists.*
>> """
>>
>> What is this exactly?
>> Can I do anything in my code to not run in to such a situation?
>>
>> Any pointers are appreciated :)
>>
>> Best regards
>> ---
>> Nicklas Overgaard
>>
>> Founder & Lead Developer
>> iSharp Solutions ApS
>>
>> _______________________________________________
>> Mono-list maillist  -  Mono-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-list
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-list/attachments/20130723/e827a9a2/attachment.html>