[protege-discussion] Fwd: Protege 3.4.4 (579) 64-bit max heap size

[Timothy Redmond]

On 09/03/2010 12:55 PM, Len Yabloko wrote:
> I got 8G on Windows 7 Professional 64-bit
>
> However, when I run Protege 3.3.4 64-bit with protege.lax set
> lax.nl.java.option.java.heap.size.max=6400000000
> I only get 1871M allocated as show below
>
> cwd: C:\Program Files\Protege_3.4.4
> cmd: "C:\Program Files\Java\jdk1.6.0_21\bin\java.exe" -Xms262144000 -Xmx2105032704 -classpath "C:\Program Files\Protege_3.4.4\protege.jar;C:\Program Files\Prote
> ge_3.4.4\looks.jar;C:\Program Files\Protege_3.4.4\unicode_panel.jar;C:\Program F
> iles\Protege_3.4.4\driver.jar;C:\Program Files\Protege_3.4.4\driver0.jar;C:\Prog
> ram Files\Protege_3.4.4\driver1.jar;C:\Program Files\Protege_3.4.4\driver2.jar$;
> C:\Program Files\Protege_3.4.4\lax.jar;" com.zerog.lax.LAX "C:/Program Files/Pro
> tege_3.4.4/Protege.lax" "C:/Users/Len/AppData/Local/Temp/laxEB4C.tmp"
> Protege 3.4.4 Build 579, JVM 1.6.0_21-b07, memory=1871M, Windows 7, encoding=UTF
> -8, language=en, country=US
>    

So I may  know about this issue. I believe that I remember a problem 
with install anywhere where it does not  properly handle the Windows 7 
64-bit case.  If you start Protege without using install-anywhere (e.g. 
by setting the right memory allocation in the run_protege.bat and 
running that) then you won't have  this problem.

This seems like it must be (??) a different problem than you originally 
reported because in the original message  you had  said:

> I have this code running inside my tab plugin:
>
> public static long test = Runtime.getRuntime().maxMemory()/1014;
>      static {
>      	System.out.println("Total memory : " +test+ " KB");
>      }
> }
>
> It results in: Total memory : 5515235 KB
>    

This is pretty much the code that Protege runs when it reports the 
memory the following output (SystemUtilities.logSystemInfo):

> Protege 3.4.4 Build 579, JVM 1.6.0_21-b07, memory=1871M, Windows 7, encoding=UTF
> -8, language=en, country=US


-Timothy


>
>
>
>
>
>
>    
>> How much physical memory do you have?   You can allocate more than
>> exits, so it just swaps pages in/out.
>> Disk light on all time after you get to that point is a clear indicator.
>> I would guess you have only 4gb real memory, so windows can only give
>> the process about 2.5 to 3gb before it has to swap
>>
>> - Stanley
>>
>> -----Original Message-----
>> From: protege-discussion-bounces at lists.stanford.edu
>> [mailto:protege-discussion-bounces at lists.stanford.edu] On Behalf Of Len
>> Yabloko
>> Sent: Friday, September 03, 2010 12:12 PM
>> To: User support for Core Protege and the Protege-Frames editor
>> Subject: Re: [protege-discussion] Protege 3.4.4 (579) 64-bit max heap
>> size
>>
>> Yes, I tried all variations and seems to corrently allocate memory.
>>
>> I have this code running inside my tab plugin:
>>
>> public static long test = Runtime.getRuntime().maxMemory()/1014;
>>     static {
>>     	System.out.println("Total memory : " +test+ " KB");
>>     }
>> }
>>
>> It results in: Total memory : 5515235 KB
>>
>> Windows 7 task manager show java.exe quickly climing to about 2G and
>> stays there. What could explain this? Do I need a specialy compiled
>> protege.jar?
>>
>>      
>>> Had you tried -Xmx6000M?
>>>
>>> http://download.oracle.com/javase/6/docs/technotes/tools/windows/java.h
>>>        
>> tml
>>      
>>> -Xmsn
>>> Specify the initial size, in bytes, of the memory allocation pool. This
>>>        
>>      
>>> value must be a multiple of 1024 greater than 1MB. Append the letter k
>>> or K to indicate kilobytes, or m or M to indicate megabytes. The
>>>        
>> default
>>      
>>> value is chosen at runtime based on system configuration.
>>>
>>> On 9/3/2010 10:57 AM, Len Yabloko wrote:
>>>        
>>>> Hello everyone,
>>>>
>>>> I am running latest Protege Frames version on Windows 7 64-bit and
>>>>          
>> trying to generate a very large frame ontology by loading data from
>> MySQL database using frame API. I have allocated 6G to jvm and checked
>> Runtime.maxMemory() to verify that is was correctly allocated. But for
>> some reason when memory reaches about 2.5G (according to Windows task
>> manager) it stops allocating and loading slows after about 15,000 frames
>> loaded. I tried launching Protege with -vmargs -Xmx6g using 64-bit jvm,
>> but no luck so far.
>>      
>>>> Can someone suggest what may be a cause of such behavior?
>>>>
>>>>
>>>> _______________________________________________
>>>> protege-discussion mailing list
>>>> protege-discussion at lists.stanford.edu
>>>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>>>
>>>> Instructions for unsubscribing:
>>>>          
>> http://protege.stanford.edu/doc/faq.html#01a.03
>>      
>>>>          
>>>
>>> _______________________________________________
>>> protege-discussion mailing list
>>> protege-discussion at lists.stanford.edu
>>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>>
>>> Instructions for unsubscribing:
>>>        
>> http://protege.stanford.edu/doc/faq.html#01a.03
>>      
>>>        
>>
>> _______________________________________________
>> protege-discussion mailing list
>> protege-discussion at lists.stanford.edu
>> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>>
>> Instructions for unsubscribing:
>> http://protege.stanford.edu/doc/faq.html#01a.03
>>
>>      
>
>
>
> _______________________________________________
> protege-discussion mailing list
> protege-discussion at lists.stanford.edu
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
>