|
|
|
|
|
by peoplewindow
3172 days ago
|
|
Well AOT even in OpenJDK is not necessarily about resource savings, just startup time. Native code is much larger than the equivalent bytecode, so compiling lots of cold code that's rarely used AOT to native can make things more bloated and slower, rather than tighter and faster. I suspect we'll see the same thing for value types: it's not going to be quite the easy win it seems. Even in C++, it's easy to create accidental footprint explosions with templates and lose performance to excessive copying with value types. And C++ allows mutable values, which are out of fashion now so Java won't allow them ... I was curious if the article would mention memory chips that knew how to do bulk memmoves by themselves. Does anyone know if memory subsystems can already do that? If you issue a memmove() for, say, 3kb of memory, does the CPU still have to read it all into the cache and then immediately write it out again, or is there some way the CPU can signal to the DRAM chips that they should do the copy themselves? Fast copying of memory would be useful for GCs. |
|