Search Mailing List Archives
[protege-discussion] Protege 3.4.4 (579) 64-bit max heap size
protege at ontospace.net
Fri Sep 3 18:47:03 PDT 2010
Thank you for all responces. I spent much of the day trying to use all available memory for loading Protege frames. The best result I got was with
-XX:MaxPermSize=3000M, although I am not sure that was it. Here is the screenshot of Windows 7 task manager showing the big plato and then sudden jump at the end. Can someone explain it?
>I would try setting the initial heap size, as well (-Xms6g). Otherwise, the
>heap must be grown over the runtime in possibly many smaller chunks, which
>can slow performance.
>On Fri, Sep 3, 2010 at 12:57 PM, Len Yabloko <protege at ontospace.net> 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:
>“Ah, but a man's reach should exceed his grasp, or what's a heaven for?”
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 251605 bytes
Desc: not available
More information about the protege-discussion