[opensource-dev] Script Memory Management Algorithm
Dickson, Mike (ISS Software)
mike.dickson at hp.com
Tue Mar 9 07:51:58 PST 2010
I'm inclined to agree. Not to mention addressed the cost of maintaining a forked version of mono and the effort to forward port it into new releases.
I suppose it's possible that a change to malloc could make script memory allocation problems much simpler but that seems highly unlikely. More likely you're trivializing a complex problem (in addition to allocation there are the issues of migrating the heap across simulators if a script moves, etc).
Mike
-----Original Message-----
From: opensource-dev-bounces at lists.secondlife.com [mailto:opensource-dev-bounces at lists.secondlife.com] On Behalf Of Argent Stonecutter
Sent: Tuesday, March 09, 2010 9:06 AM
To: Carlo Wood
Cc: server-beta at lists.secondlife.com; opensource-dev at lists.secondlife.com
Subject: Re: [opensource-dev] Script Memory Management Algorithm
On 2010-03-09, at 07:26, Carlo Wood wrote:
> This is exactly the kind of reaction that drives me away from here.
>
> I propose a simple way get FOUR times the memory for all the
> scripts, at
> no other cost than adding some malloc code to your mono engine.
I don't think you have established that.
_______________________________________________
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges
More information about the opensource-dev
mailing list