Wow! This is really exciting.
Thanks a lot, Igor. I value this help even more knowing how you feel about the modification. Or maybe you changed your mind in the meantime? :) Cheers, Doru On Jul 10, 2013, at 1:35 PM, Igor Stasenko <siguc...@gmail.com> wrote: > On 10 July 2013 00:07, Usman Bhatti <usman.bha...@gmail.com> wrote: >> Tx igor. >> Now I am waiting to get hold of the new VM (with this parameter) to test on >> Windows. >> > yes, i am building it right now on my machine to test if it works, > and jenkins refuses to build it (but for other reasons, which we need > to fix asap) > >> >> >> >> On Tue, Jul 9, 2013 at 8:44 PM, Stéphane Ducasse <stephane.duca...@inria.fr> >> wrote: >>> >>> For the people that did not click on the link :) >>> >>> Tree SHA1: 26bf913 >>> Parent SHA1: 14cc218 (- fixed save for 2.0) >>> raw diff | raw patch >>> >>> Added option in windows .ini file >>> to set the virtual memory address space limit. >>> >>> AddressSpaceLimit = <size in Mbytes> >>> The default is 512Mb >>> >>> Thanks igor. >>> >>> Stef >>> >>> >>> >>> >>> On Jul 9, 2013, at 10:03 AM, Igor Stasenko <siguc...@gmail.com> wrote: >>> >>> On 9 July 2013 09:13, Stéphane Ducasse <stephane.duca...@inria.fr> wrote: >>> >>> First, not all programming languages are like this: You can easily run >>> other VMs (e.g., Java) with more than 3 GB. But, let's not even go there: I >>> can run Pharo with 1Gb on Mac without problems. According to your reasoning >>> we might end up downgrading the Mac VM. Some data does not fit in memory, >>> but if I can get all my data in my image, I will choose to do it. >>> >>> I am not saying that we should compare with Java, or that it is the end of >>> the world that the Windows VM is highly restricted. I am simply saying that >>> we should not dismiss this as a problem just because we do not know how, or >>> do not have the resources to solve it right now. >>> >>> After all, we are here to change the world :). >>> >>> >>> Yes, but this topic was raised multiple times already. Maybe we should >>> stop wasting time on it? >>> >>> All you need to do, to change the limit, go to >>> platforms/win32/vm/sqWin32Alloc.h >>> >>> And change this: >>> >>> #ifndef MAX_VIRTUAL_MEMORY >>> #define MAX_VIRTUAL_MEMORY 512*1024*1024 >>> #endif >>> >>> So, if you want more, build VM with any limit you see fit. >>> But there's a reason why in official VM its 512. >>> >>> >>> Igor this is a real issue and we are all fighting to get more members in >>> the consortium >>> so that one day we can hire a guy like you to address it. >>> >>> >>> >>> https://gitorious.org/cogvm/blessed/commit/341e6c2e150bcde80dfea6c890bab7745b2a6d44 >>> >>> Stef >>> >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >>> >> > > > > -- > Best regards, > Igor Stasenko. > -- www.tudorgirba.com "Reasonable is what we are accustomed with."
