Hi, The discussion on this thread had nothing to do with FAMIX or Moose. It had to do with people’s ability to load larger pieces of data in the image without the VM imposing a low limit on it. There are clear scenarios where this is desirable, and I do not understand why this is a topic of conversation these days. The move to 64bit is a significant advantage in this area and we should applaud it.
Doru > On Nov 11, 2016, at 11:29 AM, Stephan Eggermont <[email protected]> wrote: > > On 10/11/16 21:35, Igor Stasenko wrote: >> No, no, no! This is simply not true. >> It is you, who writes the code that generates a lot of statistical >> data/analysis data, and its output is fairly predictable.. else you are >> not collecting any data, but just a random noise, isn't? > > That would be green field development. In brown field development, I only get > in when people start noticing there is a problem (why do we need more than > 4GBytes for this?). At that point I want to be able to load everything they > can give me in an image so I can start analyzing and structuring it. > >> I mean, Doru is light years ahead of me and many others in field of data >> analysis.. so what i can advise to him on his playground? > > Well, the current FAMIX model implementation is clearly not well structured > for analyzing large code bases. And it is difficult to partition because of > unpredictable access patterns and high interconnection. > > Stephan > > -- www.tudorgirba.com www.feenk.com "Some battles are better lost than fought."
