On Mon, Jul 29, 2013 at 7:54 AM, Ben Kloosterman <[email protected]> wrote:
> The other huge issue with GCs which relates to C4 is unless you run on a GC > based OS (Which won't happen soon ) everything has to be pinned and or > copied to and from GC managed space. That actually has to be done regardless, for security reasons. Things need to be pinned while they are being copied across spaces. In Singularity you had the shared heap (did they call it that or "exchange heap?"), but it's not enough to make data immobile; you also need to know that it is immutable or you have to copy it. That said, it's not hard to imagine a system having a "block heap" in which all blocks are of some normative size and compaction is not performed on that heap. That would deal with the I/O problem, for example. The real performance issue with I/O is that the concurrency contracts of JVM and CLR mean that you usually can't optimize the range checks out of the inner loop. It's rarely the IO *per se* that gets you. shap
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
