Memory management improvements

steve · May 24, 2011 9:09AM

From tonight's build - 2.6 b642 or later - additional memory management features have been added:

- the Memory tool (Settings > Advanced > Diagnose memory use - for advanced use only) has additional tools to monitor and free up memory that would otherwise only be reclaimed when memory was low

- the Diagnostics scheduler action has the equivalent tools and further diagnostic output

- on closing a file in Omniscope, extra effort is expended in freeing memory

- also, various memory leaks introduced in 2.6 have been fixed in the last few releases.

Note that if you're using the 64-bit version and need freed memory to be released to the operating system, you will need to configure the "-XX:+UseSerialGC" option. See http://forums.visokio.com/discussion/comment/2607/#Comment_2607

filippobe · June 3, 2011 10:10AM

Hi,

I am currently using the 32-bit and the 64 bit versions of Omniscope in parallel.
I remove the memory cap in the installconfig.properties when I switch to the 64 bit version, but I have seen that this version never releases memory, even if I close a file and I clean all the DataManager. This is a problem as I am often working with big files.

I've tried to use the Garbage collector of the memory tool, but this has no effect (the % of free memory showed in the task manager doesn't change). Therefore normally I have to save my job, close and restart Omniscope. Is there any possibility to avoid this?

Should I simply change the configuration "-XX:+UseSerialGC" even if I am using the 2 versions in parallel?

Do you have any other tips with regard to avoiding the memory's peak with big files?

Thanks,

Filippo

steve · June 3, 2011 11:04AM

It should be OK to use the XX option in both versions. Make sure you are using the latest build.

After all this, if Omniscope is still retaining memory when it should not be, open "Settings > Advanced > Diagnose memory use" and press all "clear" buttons followed by "gc". Does "used" in this dialog drop to a reasonable level (<50mb if on welcome screen, somewhat more depending on currently open data if a file is open)? Does Omniscope now release memory to the operating system?<br />

filippobe · June 6, 2011 6:47AM

Thanks Steve.
It works, but it's not automatic.
I have to use the Clear and the Gc buttons in the memory tools.

In this post: http://forums.visokio.com/discussion/comment/2607/#Comment_2607 you said I have also to update the wrapper.conf file.
Where is this file located?

Regards,
Filippo

steve · June 15, 2011 6:24AM

You only need to update wrapper.conf if you are using the windows service. The file is in your installation folder inside the service subfolder. For example:
C:\Users\Your Name\AppData\Local\Visokio Omniscope app\service\wrapper.conf

Welcome!

Categories

Ideas Parade