hi Kevin: Your patch seems requiring "USE_BLOCK_CACHE" to be enabled. Sorry for my lack of knowledge into Racket's memory management component, how can I safely enable that because I cannot find its reference in configure or Makefile.in? Thanks!
Nevo On 23 April 2011 14:27, Nevo <[email protected]> wrote: > hi Robby > Just back from out of town, sorry for the late reply. > No. This doesn't help at all, still got low-memory killing on my ipad. > Actually, my own test is all based on "#lang racket/base". I'll try Kevin's > patch to see any difference. I've also tried to throttle the > max_pages_in_heap to allow around 25MB pages to use, it will soon throw "out > of memory" exception and abort after a couple of GC cycles. > > Nevo > > > On 22 April 2011 19:08, Robby Findler <[email protected]> wrote: > >> This program: >> >> #lang racket/base >> (printf "hi\n") >> >> uses a lot less memory than this one: >> >> #lang racket >> (printf "hi\n") >> >> Does that help at all? >> >> Robby >> >> On Fri, Apr 22, 2011 at 12:09 AM, Nevo <[email protected]> wrote: >> > hi >> > My attempt on porting Racket interpreter to iOS has been for a while >> and >> > I've been able to run interpreter on both iOS device as well iOS >> simulator. >> > Right now, it runs perfectly on iOS simulator, but lack of satisfaction >> on >> > device. The reason is for those devices like iPad/iPhone or Android, the >> > memory for standalone application is always constrained, and even a >> single >> > "hello world" evaluation would easily put the whole app runtime to >> death, >> > per my test. In particular, here I've got some commented out "printf" >> code >> > compiled in for newgc.c, and trying to load a simple "hello world" >> racket >> > file to evaluate results in more than 30MB memory in use (reported by >> gc). >> > This is nothing for a desktop, but will kill itself easily in iOS which >> > usually requires the average memory allocation will be less than 20MB. >> So >> > I'm asking if there's some known compiling or runtime configuration >> which I >> > may not know to reduce memory usage, at least keep average allocation >> > acceptable for those memory constrained devices. Thanks for your >> suggests >> > here! >> > Nevo >> > _________________________________________________ >> > For list-related administrative tasks: >> > http://lists.racket-lang.org/listinfo/dev >> > >> > >
_________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
