Hi, When I open Basex 8.3 GUI, the value of the used memory keeps growing up/changing fast, even though I do not do anything. Since this does not happen with Basex 7.9, is this due to Java? (I run Java 1.8.X) Thanks, Joseph
Hi Joseph,
When I open Basex 8.3 GUI, the value of the used memory keeps growing up/changing fast, even though I do not do anything. Since this does not happen with Basex 7.9, is this due to Java? (I run Java 1.8.X)
I noticed that the memory dialog window (which is shown if you click on the memory display in the lower right corner of the GUI) is updated nonstop. Maybe you are you refering to this (unexpected) behavior? I have just added a GitHub for this [1]. If you refer to memory usage in generally, all I can say is that the memory consumption, which is indicated by a java instance, is not necessarily the amount of memory that's currently used by the JVM. I have also observed that the behavior differs with each Java version. I didn't notice any unexpected behavior by myself, but feel free to give me an update if you should encounter things like out of memory. You could e.g. limit available memory in the basexgui script to e.g. 64m, using the -Xmx64m flag, and observe if the GUI can cope with that. Best, Christian [1] https://github.com/BaseXdb/basex/issues/1118
Thanks, Joseph
Yes, I mean the value displayed in that dialog box. On my machine (Mac OS X 10.9.5), the CPU used by BaseX 8.1 turns out to be 218%, even when I am not querying anything (so I guess the memory problem causes this). If I use BaseX 7.9, everything is fine. So now I am using an older version of BaseX. I can also say that the same problem happens on another mac (OS X Yosemite 10.10.2). Thanks 2015-03-28 14:07 GMT+01:00 Christian Grün <christian.gruen@gmail.com>:
Hi Joseph,
When I open Basex 8.3 GUI, the value of the used memory keeps growing up/changing fast, even though I do not do anything. Since this does not happen with Basex 7.9, is this due to Java? (I run Java 1.8.X)
I noticed that the memory dialog window (which is shown if you click on the memory display in the lower right corner of the GUI) is updated nonstop. Maybe you are you refering to this (unexpected) behavior? I have just added a GitHub for this [1].
If you refer to memory usage in generally, all I can say is that the memory consumption, which is indicated by a java instance, is not necessarily the amount of memory that's currently used by the JVM. I have also observed that the behavior differs with each Java version.
I didn't notice any unexpected behavior by myself, but feel free to give me an update if you should encounter things like out of memory. You could e.g. limit available memory in the basexgui script to e.g. 64m, using the -Xmx64m flag, and observe if the GUI can cope with that.
Best, Christian
[1] https://github.com/BaseXdb/basex/issues/1118
Thanks, Joseph
Hi Joseph, When did you see this 218% usage of your CPU? I can replicate the behaviour when I open the said memory dialog. In this case (i.e. if the memory dialog window is open) I have also around ~200% CPU usage on my fedora machine. However, closing the window leads to a very normal CPU usage. So I would conclude the high CPU usage is simply be calculating the RAM values and updating the GUI all the time. However if you encouter this CPU usage without this memory dialog open I would say we should look into this, as it would be a non-acceptable CPU usage. Cheers Dirk On 03/30/2015 09:24 PM, Joseph wrote:
Yes, I mean the value displayed in that dialog box. On my machine (Mac OS X 10.9.5), the CPU used by BaseX 8.1 turns out to be 218%, even when I am not querying anything (so I guess the memory problem causes this). If I use BaseX 7.9, everything is fine. So now I am using an older version of BaseX.
I can also say that the same problem happens on another mac (OS X Yosemite 10.10.2). Thanks
2015-03-28 14:07 GMT+01:00 Christian Grün <christian.gruen@gmail.com>:
Hi Joseph,
When I open Basex 8.3 GUI, the value of the used memory keeps growing up/changing fast, even though I do not do anything. Since this does not happen with Basex 7.9, is this due to Java? (I run Java 1.8.X)
I noticed that the memory dialog window (which is shown if you click on the memory display in the lower right corner of the GUI) is updated nonstop. Maybe you are you refering to this (unexpected) behavior? I have just added a GitHub for this [1].
If you refer to memory usage in generally, all I can say is that the memory consumption, which is indicated by a java instance, is not necessarily the amount of memory that's currently used by the JVM. I have also observed that the behavior differs with each Java version.
I didn't notice any unexpected behavior by myself, but feel free to give me an update if you should encounter things like out of memory. You could e.g. limit available memory in the basexgui script to e.g. 64m, using the -Xmx64m flag, and observe if the GUI can cope with that.
Best, Christian
[1] https://github.com/BaseXdb/basex/issues/1118
Thanks, Joseph
-- Dirk Kirsten, BaseX GmbH, http://basexgmbh.de |-- Firmensitz: Blarerstrasse 56, 78462 Konstanz |-- Registergericht Freiburg, HRB: 708285, Geschäftsführer: | Dr. Christian Grün, Dr. Alexander Holupirek, Michael Seiferle `-- Phone: 0049 7531 28 28 676, Fax: 0049 7531 20 05 22
Yes it looks like the problem arises only when I open the dialog box. Cheers, J. Il giorno 31/mar/2015, alle ore 10:21, Dirk Kirsten <dk@basex.org> ha scritto: Hi Joseph, When did you see this 218% usage of your CPU? I can replicate the behaviour when I open the said memory dialog. In this case (i.e. if the memory dialog window is open) I have also around ~200% CPU usage on my fedora machine. However, closing the window leads to a very normal CPU usage. So I would conclude the high CPU usage is simply be calculating the RAM values and updating the GUI all the time. However if you encouter this CPU usage without this memory dialog open I would say we should look into this, as it would be a non-acceptable CPU usage. Cheers Dirk
On 03/30/2015 09:24 PM, Joseph wrote: Yes, I mean the value displayed in that dialog box. On my machine (Mac OS X 10.9.5), the CPU used by BaseX 8.1 turns out to be 218%, even when I am not querying anything (so I guess the memory problem causes this). If I use BaseX 7.9, everything is fine. So now I am using an older version of BaseX.
I can also say that the same problem happens on another mac (OS X Yosemite 10.10.2). Thanks
2015-03-28 14:07 GMT+01:00 Christian Grün <christian.gruen@gmail.com>:
Hi Joseph,
When I open Basex 8.3 GUI, the value of the used memory keeps growing up/changing fast, even though I do not do anything. Since this does not happen with Basex 7.9, is this due to Java? (I run Java 1.8.X)
I noticed that the memory dialog window (which is shown if you click on the memory display in the lower right corner of the GUI) is updated nonstop. Maybe you are you refering to this (unexpected) behavior? I have just added a GitHub for this [1].
If you refer to memory usage in generally, all I can say is that the memory consumption, which is indicated by a java instance, is not necessarily the amount of memory that's currently used by the JVM. I have also observed that the behavior differs with each Java version.
I didn't notice any unexpected behavior by myself, but feel free to give me an update if you should encounter things like out of memory. You could e.g. limit available memory in the basexgui script to e.g. 64m, using the -Xmx64m flag, and observe if the GUI can cope with that.
Best, Christian
[1] https://github.com/BaseXdb/basex/issues/1118
Thanks, Joseph
-- Dirk Kirsten, BaseX GmbH, http://basexgmbh.de |-- Firmensitz: Blarerstrasse 56, 78462 Konstanz |-- Registergericht Freiburg, HRB: 708285, Geschäftsführer: | Dr. Christian Grün, Dr. Alexander Holupirek, Michael Seiferle `-- Phone: 0049 7531 28 28 676, Fax: 0049 7531 20 05 22
This timing problem has also been fixed in... (you got it, the latest snapshot). On Tue, Mar 31, 2015 at 9:04 PM, meumapple <meumapple@gmail.com> wrote:
Yes it looks like the problem arises only when I open the dialog box.
Cheers, J.
Il giorno 31/mar/2015, alle ore 10:21, Dirk Kirsten <dk@basex.org> ha scritto:
Hi Joseph,
When did you see this 218% usage of your CPU? I can replicate the behaviour when I open the said memory dialog. In this case (i.e. if the memory dialog window is open) I have also around ~200% CPU usage on my fedora machine. However, closing the window leads to a very normal CPU usage. So I would conclude the high CPU usage is simply be calculating the RAM values and updating the GUI all the time.
However if you encouter this CPU usage without this memory dialog open I would say we should look into this, as it would be a non-acceptable CPU usage.
Cheers Dirk
On 03/30/2015 09:24 PM, Joseph wrote: Yes, I mean the value displayed in that dialog box. On my machine (Mac OS X 10.9.5), the CPU used by BaseX 8.1 turns out to be 218%, even when I am not querying anything (so I guess the memory problem causes this). If I use BaseX 7.9, everything is fine. So now I am using an older version of BaseX.
I can also say that the same problem happens on another mac (OS X Yosemite 10.10.2). Thanks
2015-03-28 14:07 GMT+01:00 Christian Grün <christian.gruen@gmail.com>:
Hi Joseph,
When I open Basex 8.3 GUI, the value of the used memory keeps growing up/changing fast, even though I do not do anything. Since this does not happen with Basex 7.9, is this due to Java? (I run Java 1.8.X)
I noticed that the memory dialog window (which is shown if you click on the memory display in the lower right corner of the GUI) is updated nonstop. Maybe you are you refering to this (unexpected) behavior? I have just added a GitHub for this [1].
If you refer to memory usage in generally, all I can say is that the memory consumption, which is indicated by a java instance, is not necessarily the amount of memory that's currently used by the JVM. I have also observed that the behavior differs with each Java version.
I didn't notice any unexpected behavior by myself, but feel free to give me an update if you should encounter things like out of memory. You could e.g. limit available memory in the basexgui script to e.g. 64m, using the -Xmx64m flag, and observe if the GUI can cope with that.
Best, Christian
[1] https://github.com/BaseXdb/basex/issues/1118
Thanks, Joseph
-- Dirk Kirsten, BaseX GmbH, http://basexgmbh.de |-- Firmensitz: Blarerstrasse 56, 78462 Konstanz |-- Registergericht Freiburg, HRB: 708285, Geschäftsführer: | Dr. Christian Grün, Dr. Alexander Holupirek, Michael Seiferle `-- Phone: 0049 7531 28 28 676, Fax: 0049 7531 20 05 22
participants (4)
-
Christian Grün -
Dirk Kirsten -
Joseph -
meumapple