Re: [pypy-dev] minimum system requirements, build configuration

2011-04-05 Thread Liam Staskawicz
Indeed - great to see some of the thought going into this area of the project :) If I make any progress on the actual HW I'll be sure to let you know. Liam On Tue, Apr 5, 2011 at 1:51 PM, Dima Tisnek wrote: > Hi Armin, thanks for pointing me in the right direction. > > If minimark.py docstring

Re: [pypy-dev] minimum system requirements, build configuration

2011-04-05 Thread Dima Tisnek
Hi Armin, thanks for pointing me in the right direction. If minimark.py docstring is up to date, looks like it will do close to the right thing on arm5/9. Some of the older arms don't have L2 cache, I'm not sure what /proc/cpuinfo reports in this case, perhaps L1 cache size or nothing. It seems i

Re: [pypy-dev] minimum system requirements, build configuration

2011-04-05 Thread Armin Rigo
Hi Dima, On Tue, Apr 5, 2011 at 9:52 PM, Dima Tisnek wrote: > What I mean > to say is that there's gotta be a more clever way where gc thresholds > depend on e.g. size of working set or rate of new allocations or > something yet smarter. Yes, it does in PyPy; we do a full collection when the tot

Re: [pypy-dev] minimum system requirements, build configuration

2011-04-05 Thread Dima Tisnek
Oh, I guessed your reasons. Lanugages like python make a lot of garbage, so 16MB will fill up pretty fast as long as the program does something at all. What I mean to say is that there's gotta be a more clever way where gc thresholds depend on e.g. size of working set or rate of new allocations or

Re: [pypy-dev] minimum system requirements, build configuration

2011-04-05 Thread Armin Rigo
Hi Dima, On Tue, Apr 5, 2011 at 9:26 PM, Dima Tisnek wrote: > What I'm trying to say, is gc should adapt to run-time behaviour of a > particular script, in some cases 16MB heap threshold would impact both > user expectation and performance significantly. It may impact user expectation and perfor

Re: [pypy-dev] minimum system requirements, build configuration

2011-04-05 Thread Dima Tisnek
On 5 April 2011 08:54, Armin Rigo wrote: [snip] > I'm rather confident than 64MB is enough, but I also guess that 32MB > has a chance to work.  With only 16MB I bet nothing much works right > now (given that e.g. our GC, by default, does not collect before the > heap grew to at least 16MB).  It ma

Re: [pypy-dev] minimum system requirements, build configuration

2011-04-05 Thread Armin Rigo
Hi, On Tue, Apr 5, 2011 at 5:08 PM, Liam Staskawicz wrote: > This is correct, the non-jitted version can be cross-translated to > ARM. Although it still only supports the Boehm GC I think that you are saying something wrong: "no jit + our own GC + the shadowstack gc root finder" should get you p

Re: [pypy-dev] minimum system requirements, build configuration

2011-04-05 Thread Liam Staskawicz
Hi David, thanks for the quick response. On Tuesday, April 5, 2011 at 7:18 AM, David Schneider wrote: > Hi Liam, > > On Tue, Apr 5, 2011 at 07:25, Liam Staskawicz wrote: > > Hi - I've been looking at pypy as a possible application runtime in an ARM9 > > Linux based system. I understand that the

[pypy-dev] minimum system requirements, build configuration

2011-04-04 Thread Liam Staskawicz
Hi - I've been looking at pypy as a possible application runtime in an ARM9 Linux based system. I understand that the in-progress ARM jit backend targets only ARMv7, but I'm still interested in characterizing a translated pypy-c interpreter on this system with regard to CPU and memory usage. Of