On Thu, Nov 10, 2016 at 10:31 AM, Denis Kudriashov <[email protected]> wrote:
> > 2016-11-10 9:49 GMT+01:00 [email protected] <[email protected]>: > >> Ah, but then it may be more interesting to have a data image (maybe a lot >> of these) and a front end image. >> >> Isn't Seamless something that could help us here? No need to bring the >> data back, just manipulate it through proxies. >> > > Problem that server image will anyway perform GC. And it will be slow if > server image is big which will stop all world. > What if we asked it to not do any GC at all? Like if we have tons of RAM, why bother? Especially if what it is used to is to keep datasets: load them, save image to disk. When needed trash the loaded stuff and reload from zero. Basically that is what happens with Spark. http://sujee.net/2015/01/22/understanding-spark-caching/#.WCRIgy0rKpo https://0x0fff.com/spark-misconceptions/ and Tachyon/Alluxio is kind of solving this kind of issue (may be nice to have that interacting with Pharo image). http://www.alluxio.org/ This thing basically keeps stuff in memory in case one needs to reuse the data between workload runs. Or have an object memory for work and one for datasets (first one gets GC'd, the other one isn't). Phil
