Dan Sugalski <[EMAIL PROTECTED]> wrote:
> Well, I just committed a change to the system that should speed up
> object creation a bunch, as it doesn't need to allocate a vtable for
> each object any more.
Please cvs update and have a look at benchmarks/oo*. I'v speeded object
creation up by a facto
At 8:20 PM +0100 3/4/04, Leopold Toetsch wrote:
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
- its slow (unoptimized build for now - but that doesn't matter yet)
Some more remarks to that.
- Python is around at double the speed of perl here
- Parrot seems to take too much time in delegate.pmc:
-
At 9:04 AM -0800 3/4/04, Larry Wall wrote:
On Thu, Mar 04, 2004 at 09:58:02AM -0500, Dan Sugalski wrote:
: Damn. Okay, I'm going to spend today digging into the object stuff to
: try and track down the leaks. Something's not right in there, as the
: DOD and GC ought to be reclaiming the dead memory
Dan Sugalski wrote:
At 3:36 PM +0100 3/4/04, Leopold Toetsch wrote:
I've run these 2 tests below.
Results don't look really good.
Damn. Okay, I'm going to spend today digging into the object stuff to
try and track down the leaks. Something's not right in there, as the DOD
and GC ought to be re
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> - its slow (unoptimized build for now - but that doesn't matter yet)
Some more remarks to that.
- Python is around at double the speed of perl here
- Parrot seems to take too much time in delegate.pmc:
- register preserving
- method lookup
- reen
On Thu, Mar 04, 2004 at 09:58:02AM -0500, Dan Sugalski wrote:
: Damn. Okay, I'm going to spend today digging into the object stuff to
: try and track down the leaks. Something's not right in there, as the
: DOD and GC ought to be reclaiming the dead memory.
Can I hit you with a cream pie at OSCO
At 3:36 PM +0100 3/4/04, Leopold Toetsch wrote:
I've run these 2 tests below.
Results don't look really good.
- Parrot consumes ever increasing memory, so it can't even run up to 10
- its slow (unoptimized build for now - but that doesn't matter yet)
- Parrot is leaking a vtable per new class