Here's a comparison of the memory (MB) and the CPU (ms) usage.
Memory Comparison - http://www.flickr.com/photos/92143...@n00/3859425885/
CPU Comparison - http://www.flickr.com/photos/92143...@n00/3860208646/
new cont - don't force gc means a new continuation is created for each
iteration of the
Oh and here's the actual data
http://spreadsheets.google.com/pub?key=tYFncjADIjzq3rtmWF6EWdwoutput=html
On Wed, Aug 26, 2009 at 4:19 PM, James Zhao jameszha...@gmail.com wrote:
Here's a comparison of the memory (MB) and the CPU (ms) usage.
Memory Comparison -
Hi,
Here's Mono Continuations' continuation_store (...). From looking at the
code below, it appears as though store() follows these two branches:
1. cont-saved_stack num_bytes = cont-stack_alloc_size - use the memory
directly
2. else - gc free the used memory, and create some new memory.
Hi,
mono_gc_free_fixed () is a no-op when using mono's built in GC, since
mono_gc_alloc_fixed () is implemented as a call to GC_malloc ().
Zoltan
On Wed, Aug 26, 2009 at 2:55 AM, James Zhao jameszha...@gmail.com wrote:
Hi,
Here's Mono Continuations' continuation_store
Hi,
Thank you for that info. So that means if current stack last stack, the
stack pointer is C freed and malloced. If that's the case, then the behavior
I've been experiencing is even more bizarre.
Also, you mentioned the built-in gc. What other GCs are available?
Thanks,
James
On Tue, Aug
On Wed, Aug 26, 2009 at 3:11 AM, James Zhao jameszha...@gmail.com wrote:
Hi,
Thank you for that info. So that means if current stack last stack, the
stack pointer is C freed and malloced. If that's the case, then the behavior
I've been experiencing is even more bizarre.
Also, you
