On Aug 2, 2012, at 10:28 PM, Stéphane Ducasse stephane.duca...@inria.fr wrote:
On Aug 2, 2012, at 10:17 PM, jannik.laval wrote:
Hi,
I tried the VM included in Moose (moosetechnology.org).
If I remember well, it is a cog vm.
The maximal heap size is (precisely): 2138046463 bytes.
Not bad :)
Doru
On Fri, Aug 3, 2012 at 8:11 AM, jannik.laval jannik.la...@gmail.com wrote:
On Aug 2, 2012, at 10:28 PM, Stéphane Ducasse stephane.duca...@inria.fr
wrote:
On Aug 2, 2012, at 10:17 PM, jannik.laval wrote:
Hi,
I tried the VM included in Moose (moosetechnology.org).
If I
so this means that the comment of Fabrizio about the limit of 500 mb was only
for windows.
Stef
Not bad :)
Doru
On Fri, Aug 3, 2012 at 8:11 AM, jannik.laval jannik.la...@gmail.com wrote:
On Aug 2, 2012, at 10:28 PM, Stéphane Ducasse stephane.duca...@inria.fr
wrote:
On Aug 2,
Yes, for Windows, 500MB is a rather hard limit with Cog. I bump into it all the
time :(.
But, I think the experiment of Jannik was done with the special 64-bit VM.
Jannik, am I right?
Cheers,
Doru
On 3 Aug 2012, at 15:00, Stéphane Ducasse wrote:
so this means that the comment of Fabrizio
No, no,
The experiment was made with the VM included in the one-click Moose, in a MacOs
X 10.8.
For now, I do not succeed to use the 64bit VM and build a usable 64bit image.
Jannik
On Aug 3, 2012, at 10:09 PM, Tudor Girba tu...@tudorgirba.com wrote:
Yes, for Windows, 500MB is a rather hard
Yes, for Windows, 500MB is a rather hard limit with Cog. I bump into it all
the time :(.
I imagine well, believe me and I'm a bit sad about all the story around VMs.
I see all the infrastructure that igor built and there is not much cooperation
around it even if esteban happily uses it
and
Guillermo Polito has been updating SystemTracer to latest Pharo (and Cog).
I think you should try to use that.
On Wed, Aug 1, 2012 at 11:54 PM, Stephan Eggermont step...@stack.nl wrote:
Dave wrote:
Please try the 64bitImage*64bitVM image from John's site here:
On Thu, Aug 2, 2012 at 9:40 AM, Mariano Martinez Peck
marianop...@gmail.com wrote:
Guillermo Polito has been updating SystemTracer to latest Pharo (and Cog). I
think you should try to use that.
Yeap, but it I'd not call it an update :). It is more a complete
refactor to make it more
Guile wrote:
Yeap, but it I'd not call it an update :). It is more a complete refactor
to make it more understandable to newbies like me.
Anyway, I didn't migrate the code to write 64bit image,
and I'm not planning to do it in the short term...
If you want to take a look, the project is in
Thank you !
I will try it in few days.
Cheers,
Jannik
On Aug 1, 2012, at 8:35 PM, David T. Lewis le...@mail.msen.com wrote:
On Wed, Aug 01, 2012 at 09:04:20AM -0400, John McIntosh wrote:
I'm sure I built a vm for 64 bits a few years back, maybe not a stack one,
can't remember
ya
Hi,
I tried the VM included in Moose (moosetechnology.org).
If I remember well, it is a cog vm.
The maximal heap size is (precisely): 2138046463 bytes.
Why this number ? I don't know. But I will need more than 2Gb.
I will try the 64bits vm, and see.
Cheers,
Jannik
On Aug 1, 2012, at 7:51 PM,
On Aug 2, 2012, at 10:17 PM, jannik.laval wrote:
Hi,
I tried the VM included in Moose (moosetechnology.org).
If I remember well, it is a cog vm.
The maximal heap size is (precisely): 2138046463 bytes.
Why this number ? I don't know. But I will need more than 2Gb.
HI jannik
was the
On Jul 31, 2012, at 11:46 PM, johnmci wrote:
David Lewis and I spent a far amount of time a few years back to make the 32
vm 4gb clean. So are you running on stale knowledge here, or does the vm
crash when to goes over 2gb?
sorry my english limit does not let me know understanding what you
A few years back the interpreted virtual machine was fixed to allow an
image to grow to the 4 GB limit.
It is unclear to me if someone regressed the software to impose a 2GB limit
again, or if the 2GB number
mentioned is based on how things worked10 years ago?
On Wed, Aug 1, 2012 at 5:01 AM,
I'm sure I built a vm for 64 bits a few years back, maybe not a stack one,
can't remember
ya
http://lists.squeakfoundation.org/pipermail/vm-dev/2010-January/003732.html
On Tue, Jul 31, 2012 at 11:01 AM, David T. Lewis le...@mail.msen.comwrote:
I don't know of anyone who has built a StackVM for
On 1 August 2012 14:57, John McIntosh john...@smalltalkconsulting.com wrote:
A few years back the interpreted virtual machine was fixed to allow an image
to grow to the 4 GB limit.
It is unclear to me if someone regressed the software to impose a 2GB limit
again, or if the 2GB number
Hi John,
There is no regression in the interpreter VM ... well actually there was
about 6 months back, but I keep an eye on it and it's fixed again now :)
The 32-bit interpreter VM will not fail on any 2GB or 4BG boundaries,
and an interpreter VM compiled for the 64-bit object format can handle
On Wed, Aug 01, 2012 at 09:04:20AM -0400, John McIntosh wrote:
I'm sure I built a vm for 64 bits a few years back, maybe not a stack one,
can't remember
ya
http://lists.squeakfoundation.org/pipermail/vm-dev/2010-January/003732.html
John:
Thanks, I had forgotten about your 64*64 VM, I think
Dave wrote:
Please try the 64bitImage*64bitVM image from John's site here:
ftp://ftp.smalltalkconsulting.com/experimental/64bit/
Loads and runs on my 10.7.3 MBA.
If you can run that VM on your Mac, it should do exactly what you need.
Try running that VM with one of your images. If it runs and
Hi Dave,
I begin with a small problem (is it ?): my os is the latest apple macos.
It seems that there is no squeak vm 64 for macos (I did not find it).
How can I build one easily ?
Thanks,
Jannik
On Jul 24, 2012, at 2:04 PM, David T. Lewis le...@mail.msen.com wrote:
On Tue, Jul 24, 2012 at
Hi Jannik,
I am not a Mac user, and I have only ever done this on Linux, so I cannot
promise that it will be easy. Possibly Esteban can give us some advice here,
and correct my errors. Also, if you are going to try this, we may want to
take the discussion to the vm-dev list.
You will need to
Hi guys,
I've been building the iOS StackVM for my own uses and am definitely
interested in getting a 64-bit StackVM for some large data sets I'd like to
load in RAM for some experiments.
If there are pointers given, I am willing to test the build on my box.
Phil
2012/7/31 David T. Lewis
I don't know of anyone who has built a StackVM for the 64-bit object memory,
so this might require some development work. It would certainly be possible
to do it, but I don't think that anyone has tried.
Note that Eliot has plans for improved object memory formats, and the current
64-bit object
esteban has been fighting all day to compile the vm on mountain lion.
A problem with free type plugin not found dylib and friends.
Hi Jannik,
I am not a Mac user, and I have only ever done this on Linux, so I cannot
promise that it will be easy. Possibly Esteban can give us some advice
David Lewis and I spent a far amount of time a few years back to make the 32
vm 4gb clean. So are you running on stale knowledge here, or does the vm
crash when to goes over 2gb?
--
View this message in context:
http://forum.world.st/Memory-usage-tp4641108p4642349.html
Sent from the Pharo
Hi Dave,
Should I load the SystemTracer available on SqueakSource ? The last version is
from 2011, and seems old, no ?
When I try it, it calls some methods that do not exist in Pharo.
Do you have more information on how to use it ?
Cheers,
Jannik
On Jul 23, 2012, at 2:15 PM, David T. Lewis
Iep, I will keep all the informations and write a document.
Jannik
On Jul 23, 2012, at 2:41 PM, Tudor Girba wrote:
The prospect sounds exciting.
Jannik, if you do manage to get this to work with Moose, it would be
great to document it :)
Cheers,
Doru
On Mon, Jul 23, 2012 at 2:15 PM,
On Tue, Jul 24, 2012 at 09:27:49AM +0200, jannik.laval wrote:
Hi Dave,
Should I load the SystemTracer available on SqueakSource ? The last version
is from 2011, and seems old, no ?
When I try it, it calls some methods that do not exist in Pharo.
Do you have more information on how to use
Dear pharoers,
We are loading really big models in the Moose software analysis platform.
This generate a lot of small objects and with the biggest model, we approach
the limit of 2Gb of the VM.
Is it possible for anyone who knows the VM to add extra memory space ? Going to
4Gb or maybe 8Gb
On Mon, Jul 23, 2012 at 09:26:18AM +0200, jannik.laval wrote:
Dear pharoers,
We are loading really big models in the Moose software analysis platform.
This generate a lot of small objects and with the biggest model, we approach
the limit of 2Gb of the VM.
Is it possible for anyone who
The prospect sounds exciting.
Jannik, if you do manage to get this to work with Moose, it would be
great to document it :)
Cheers,
Doru
On Mon, Jul 23, 2012 at 2:15 PM, David T. Lewis le...@mail.msen.com wrote:
On Mon, Jul 23, 2012 at 09:26:18AM +0200, jannik.laval wrote:
Dear pharoers,
We
31 matches
Mail list logo
