Search Mailing List Archives
[protege-discussion] Protege 3.4.4 (579) 64-bit max heap size
swt at stanford.edu
Fri Sep 3 11:57:08 PDT 2010
Had you tried -Xmx6000M?
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
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
More information about the protege-discussion