Re: Switch from SBCL to Erlang backend due to scalability issues(GC).
- From: Wade Humeniuk <whumeniu+anti+spam@xxxxxxxxx>
- Date: Tue, 06 Mar 2007 14:40:53 GMT
Matthew Swank wrote:
http://lambda-the-ultimate.org/node/2102
This seems to making the rounds; though Lisp is still used as a source
language then compiled to Erlang.
From the developers comments ....
<quote>
The "benchmark code" is difficult to isolate. It's not like we're computing fibbonaci sequences here... there has to be a stream of events coming in from real-world users. SBCL starts to use an insane amount of memory, and the footprint grows even though the set of reachable objects (essentially we use the interal functions (room) calls to walk the objects, and the output of (room) itself) doesn't get much bigger. It's been a while since we've run any numbers on this problem so I don't have any handy.
Clearly something changed with the garbage collector in more recent versions of SBCL -- now SBCL uses 100% CPU all the time in production and lasts much longer before finally bombing due to exhaustion of its pre-committed space.
And we aren't using OS-level threads at all.
By a1k0n at Mon, 2007-03-05 17:39 | login or register to post comments
</quote>
The question is... what are the SBCL group going to do about it? Sounds like
they have messed up (maybe by tinkering too much?). Screwed the pooch. Of course
the Vendetta developers should have known better then use beta software. It is
getting tiring that computer languages are getting bad reps because of human
screw-ups. Just Fix It!!!
Wade
.
- Follow-Ups:
- Re: Switch from SBCL to Erlang backend due to scalability issues(GC).
- From: Wade Humeniuk
- Re: Switch from SBCL to Erlang backend due to scalability issues(GC).
- From: Ken Tilton
- Re: Switch from SBCL to Erlang backend due to scalability issues(GC).
- From: Tim Bradshaw
- Re: Switch from SBCL to Erlang backend due to scalability issues(GC).
- From: Juho Snellman
- Re: Switch from SBCL to Erlang backend due to scalability issues(GC).
- References:
- Switch from SBCL to Erlang backend due to scalability issues(GC).
- From: Matthew Swank
- Switch from SBCL to Erlang backend due to scalability issues(GC).
- Prev by Date: Case of a reader macro character
- Next by Date: Re: Switch from SBCL to Erlang backend due to scalability issues(GC).
- Previous by thread: Re: Switch from SBCL to Erlang backend due to scalability issues(GC).
- Next by thread: Re: Switch from SBCL to Erlang backend due to scalability issues(GC).
- Index(es):
Relevant Pages
|
