Hello again Dave!

I just tested this on my machine and for some reason it doesn't work with
too big values (different error messages at different levels).

Here are my observations of the limits:
Windows (real 512M maximum Paging file size 1536): 1470M
Linux (real 128M swap area 780M): 1850M
Linux (real 192M swap area 292M WMWare within the Windows machine above):
2632M

This is probably not an as simple issue as I thought. Perhaps we should
stick to 512M as the default.

        /Linus


2008/5/31, Dave Thompson <[EMAIL PROTECTED]>:
>
> Linus Tolke wrote:
>
>> For Java Web Start and the .sh and .bat files I think we have set 512M.
>>
>
> For .sh and .bat, there is no setting currently:
>
>
> http://argouml.tigris.org/source/browse/*checkout*/argouml/trunk/src/argouml-app/src/bin/argouml.bat?rev=14755
>
> http://argouml.tigris.org/source/browse/*checkout*/argouml/trunk/src/argouml-app/src/bin/argouml.sh?content-type=text%2Fplain&rev=14757
>
> I think that the value should be approximately the amount of real memory in
>> the machine running ArgoUML. 512M was a reasonable at the time it was set
>> because developers used 512M or could upgrade their machines to. Nowadays 2G
>> would probably be a more appropriate figure with this reasoning since most
>> machines are sold with 2G but there are other scalability problems that I
>> guess makes working with ArgoUML on large models unbearable. I am just not
>> sure where the level is.
>>  If you want to change, I suggest you increase to 2G or 4G. This will
>> allow users working with really big models without thinking about the memory
>> problem.
>>
>
> I assume that a setting of -Xms2048m would not prevent ArgoUML from running
> on a machine with less memory, it would just result in a lot of paging to
> disc (assuming the disc space is available).
>
> If this is OK, I'll make the change.
>
> Dave
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to