Re: [racket-dev] Memory consumption of Racket

2011-04-23 Thread Nevo
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 ro...@eecs.northwestern.edu 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 sakur.dea...@gmail.com 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

Re: [racket-dev] Optional equality predicate for assoc and member

2011-04-23 Thread Eli Barzilay
9 hours ago, Noel Welsh wrote:
 On Sat, Apr 23, 2011 at 12:52 AM, Eli Barzilay e...@barzilay.org wrote:
  Is there some obvious reason for the huge difference in
  improvement between the 32 and the 64 bits (Almost twice slower
  and roughly the same resp.)?
 
 My guess is that this benchmark is dominated by memory access time,
 and on 64-bit machines you're shifting twice as much memory.

That doesn't explain how it becomes so much faster...  Actually, the
exceptional result is the C version on 32 bit: JIT on 32, JIT on 64,
and C on 64 are all very close, and only C on 32 is about twice
faster.

-- 
  ((lambda (x) (x x)) (lambda (x) (x x)))  Eli Barzilay:
http://barzilay.org/   Maze is Life!
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev


Re: [racket-dev] Pre-Release Checklist for v5.1.1

2011-04-23 Thread Michael Sperber

Ryan Culpepper ry...@ccs.neu.edu writes:

 * Mike Sperber sper...@deinprogramm.de
   - DMdA Tests
   - Stepper Tests
   - Signature Tests

Pending the merge of 7f9bd528573ddbe5c3b4607e0b9d842e93662427 into the
release branch, done.  (Thanks, Robby!)

-- 
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev


Re: [racket-dev] Pre-Release Checklist for v5.1.1

2011-04-23 Thread Gregory Cooper

 * Greg Cooper g...@cs.brown.edu
  - FrTime Tests


Done.
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev

Re: [racket-dev] Pre-Release Checklist for v5.1.1

2011-04-23 Thread Eli Barzilay
Two days ago, Jon Rafkind wrote:
 
  * Jon Rafkind rafk...@cs.utah.edu
Release tests for (one of the) linux releases:
- Test that the `racket' and `racket-textual' source releases
  compile fine
- Test that the binary installers for both work, try each one in
  both normal and unix-style installation modes. (just ubuntu)
[Note: get the release candidates from the URL in this email. Use
 the 'static table' link to see a list of all tar files available]
 
 The binary installers had problems with libffi.so.5. Source
 distributions are still compiling. [...]

Should be fixed now, can you retry?

-- 
  ((lambda (x) (x x)) (lambda (x) (x x)))  Eli Barzilay:
http://barzilay.org/   Maze is Life!
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev


Re: [racket-dev] Pre-Release Checklist for v5.1.1

2011-04-23 Thread Robby Findler
On Sat, Apr 23, 2011 at 7:28 AM, Michael Sperber
sper...@deinprogramm.de wrote:

 Ryan Culpepper ry...@ccs.neu.edu writes:

 * Mike Sperber sper...@deinprogramm.de
   - DMdA Tests
   - Stepper Tests
   - Signature Tests

 Pending the merge of 7f9bd528573ddbe5c3b4607e0b9d842e93662427 into the
 release branch, done.  (Thanks, Robby!)

I hate to be a pest, but do you mind re-running your tests now that we
have a build with my commit in it?

Also: anyone else who has the energy to fiddle with the teaching
languages a bit, doing some fiddling now would be helpful

Thanks,
Robby

_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev

Re: [racket-dev] Pre-Release Checklist for v5.1.1

2011-04-23 Thread Matthias Felleisen

On Apr 23, 2011, at 2:08 PM, Robby Findler wrote:

 Also: anyone else who has the energy to fiddle with the teaching
 languages a bit, doing some fiddling now would be helpful


I will be fiddling when I do my checks. I tend to wait these days to go as one 
of the last ones. 
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev


[racket-dev] Pre-Release Checklist for v5.1.1, second call

2011-04-23 Thread Ryan Culpepper
Checklist items for the v5.1.1 release
  (using the v5.1.0.900 release candidate build)

Search for your name to find relevant items, reply when you finish an
item (please indicate which item/s is/are done).  Also, if you have any
commits that should have been picked, make sure that the changes are in.

Important: new builds are created without announcement, usually whenever
I pick a few commits.  If you need to commit changes, please make sure
you tell me to pick it into the release branch.

-- Release candidates are at
--   http://pre.racket-lang.org/release/installers

Please use these installers (or source bundles) -- don't test from
your own git clone (don't test v5.1.1.1 by mistake!).  To get
the tests directory in such a directory, you can do this:
  cd ...racket-root...
  git archive --remote=git://git.racket-lang.org/plt.git release \
  -- collects/tests | tar x

--

* Matthias Felleisen matth...@ccs.neu.edu
  - Teachpacks Tests: check that new teachpacks are addable
  - Teachpack Docs: check teachpack docs in the bundles
  Updates:
  - Teachpack Updates: update HISTORY
  (updates should show v5.1.1 as the most current version; email me
  to pick the changes when they're done, or tell me if there are no such
  changes.)

* Kathy Gray kathryn.g...@cl.cam.ac.uk
  - Test Engine Tests

* Noel Welsh noelwe...@gmail.com
  - Rackunit Tests
  - SRFI Tests
  - Ensure that all claimed srfi's are in the installer and they all
load into racket or drracket (as appropriate)

* Stephen Chang stch...@ccs.neu.edu
  - Lazy Racket Tests
  - Lazy stepper tests

* Eli Barzilay e...@barzilay.org
  - Racket Tree: compare new distribution tree to previous one

* Jon Rafkind rafk...@cs.utah.edu
  Release tests for (one of the) linux releases:
  - Test that the `racket' and `racket-textual' source releases
compile fine
  - Test that the binary installers for both work, try each one in
both normal and unix-style installation modes. (just ubuntu)
  [Note: get the release candidates from the URL in this email. Use
   the 'static table' link to see a list of all tar files available]

-- 
Ryan Culpepper
_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev


[racket-dev] Universe and Redex

2011-04-23 Thread David Van Horn
Sam and I have been teaching a first year course on programming and our 
final project is a distributed, multi-player game similar to this one:


   http://www.gamedesign.jp/flash/dice/dice.html

Students had to write clients, servers, and AI players, and during our 
final exam period, we're going to hold a tournament between all the AI 
players -- hosted on a server that Sam and I wrote.


One idea that we had, which turned out to be a good one, was to define 
the language of client to server messages as a Redex language and then 
use Redex's random term generation to stress test our server.  We 
constructed simple clients that did a rapid-fire send of random 
messages.  We tested on well-formed messages, messages that were close 
to being well-formed, and messages that were just arbitrary junk (all 
expressed in a couple lines using define-language).  We found several 
bugs in our server and running our students' clients against the server 
has not uncovered any further bugs beyond what Redex found.


David
_
 For list-related administrative tasks:
 http://lists.racket-lang.org/listinfo/dev


Re: [racket-dev] Universe and Redex

2011-04-23 Thread Neil Van Dyke

David Van Horn wrote at 04/23/2011 09:12 PM:
was to define the language of client to server messages as a Redex 
language and then use Redex's random term generation to stress test 
our server.


Would be interesting to see how this work with Redex would be framed 
within related work.  There is a popular broad term, fuzz testing.


--
http://www.neilvandyke.org/
_
 For list-related administrative tasks:
 http://lists.racket-lang.org/listinfo/dev


Re: [racket-dev] Universe and Redex

2011-04-23 Thread Robby Findler
On Sat, Apr 23, 2011 at 8:23 PM, Neil Van Dyke n...@neilvandyke.org wrote:
 David Van Horn wrote at 04/23/2011 09:12 PM:

 was to define the language of client to server messages as a Redex
 language and then use Redex's random term generation to stress test our
 server.

 Would be interesting to see how this work with Redex would be framed within
 related work.  There is a popular broad term, fuzz testing.

There is a huge pile of work on random testing. See our papers for a
start on citations.

Robby

_
  For list-related administrative tasks:
  http://lists.racket-lang.org/listinfo/dev