> On Dec 9, 2015, at 4:35 PM, Rick Mann <[email protected]> wrote:
> 
>> 
>> On Dec 9, 2015, at 16:24 , David Duncan <[email protected]> wrote:
>> 
>> 
>>> On Dec 9, 2015, at 3:36 PM, Rick Mann <[email protected]> wrote:
>>> 
>>> 
>>>> On Dec 9, 2015, at 15:19 , Jens Alfke <[email protected]> wrote:
>>>> 
>>>> 
>>>>> On Dec 9, 2015, at 2:56 PM, Rick Mann <[email protected]> wrote:
>>>>> 
>>>>> One of the WWDC videos stressed that iOS apps are given no more than 600 
>>>>> MB of RAM. Our app is VERY RAM-intensive. 
>>>> 
>>>> Slightly off-topic, but I wonder if you could use mmap to give your app 
>>>> more address space? Create a big empty file, mmap it as writeable, then 
>>>> use a custom allocator to manage memory in the mapped space.
>>>> 
>>>> (This doesn’t actually give you more RAM; the mapped address space will 
>>>> tend to get paged out to storage so it’ll definitely be slower than real 
>>>> RAM, but it’s better than crashing!)
>>> 
>>> That's an interesting thought. We're also very compute intensive, so the 
>>> speed hit might obviate the advantages. Worth considering, though.
>> 
>> The virtual limit is 2GB on most devices right now, so you can use mmap() to 
>> go beyond the dirty limit.
> 
> Hi. Sorry, can you elaborate on that? Is the "virtual limit" the thing that 
> used to be 600 MB? What's the dirty limit, and how does it compare with the 
> virtual limit?

The virtual limit is how much virtual memory you can use. The dirty limit is 
how much dirty memory you can use. The dirty limit is the limit you had heard 
previously, I think 650MB on most devices.

> 
> Thanks,
> 
> 
> -- 
> Rick Mann
> [email protected] <mailto:[email protected]>
--
David Duncan

_______________________________________________

Cocoa-dev mailing list ([email protected])

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to