http://forums.visokio.com/discussions/tagged/memory-management/feed.rss Mon, 30 Oct 17 12:23:38 -0400 Tagged with memory-management - Visokio Forums en-CA http://forums.visokio.com/discussion/1650/memory-management-32-bit-limit-exceeded-on-64-bit-machines Fri, 13 Jul 2012 13:55:24 -0400 Alexander 1650@/discussions As it is in the command screen, and not in Omniscope itself, I cannot send an error report.

I attached a screenshot, if you need any additional info please let me know. Thanks!]]> http://forums.visokio.com/discussion/3044/performance-memory-management-on-a-virtual-server Fri, 27 Nov 2015 03:57:18 -0500 enrico68 3044@/discussions The operating system that manage the virtual machines on this physical server is VMWare 5.1 and Omniscope version is the 2.9 Server.

Since datasets we are elaborating are growing up in dimensions quite rapidly, we have now changed the configuration in a way that the virtual memory used can be extended up to 32Gb and the number of virtual processors can be extended up to 8, if these resources are available (not used by other virtual machines) on the physical server where the virtual machine is installed.

We are now running some large .iok file update for testing the new server configuration, but till now Omniscope has always used at most the usual 16Gb of memory and, sincerly, I do not think that the problem is that there are no other resource available.

I'd like to know if there is a particular set up to perform to let Omniscope see and use the new available memory and processors or if anyone has experience to share about using Omniscope on virtual server.]]> http://forums.visokio.com/discussion/2403/performance-setting-memory-on-windows-8s Fri, 15 Nov 2013 06:05:56 -0500 daniel 2403@/discussions
http://www.visokio.com/kb/omniscope-memory-allocation]]> http://forums.visokio.com/discussion/2031/idea-performance-switching-between-ssd-disk-and-memorys Fri, 01 Mar 2013 06:57:32 -0500 martingurner 2031@/discussions
We have issues where a 22mb file can take up to 30 minutes loading on 64xWin7 with 16gigs of RAM. During this time, the RAM will increase to all available RAM and stay until the file is closed.]]> http://forums.visokio.com/discussion/1580/max-memory-issue Wed, 06 Jun 2012 08:41:38 -0400 alec_webliquid 1580@/discussions
I am trying out Omniscope on a new machine, using a trial license, and am puzzled by the maximum amount of memory it says is available (obtained by Help --> About --> Max memory). I am running 64-bit Omniscope on Windows 7 Professional 64-bit, with 16GB RAM, however the amount available is only 1936MB and the performance of the program certainly reflects this. Surely it should default to 75% * 16GB = 12GB? This is a fresh install with no config options changed. I installed for all users. I had the same issue when trying it out on a virtual machine also.

Help and/or advice would be much appreciated!

Cheers]]> http://forums.visokio.com/discussion/1655/scheduler-performance-issues Mon, 16 Jul 2012 10:41:41 -0400 Alexander 1655@/discussions Is this a setting somewhere? I adapted the installconfig to use more then 75% of the RAM. - Thanks]]> http://forums.visokio.com/discussion/864/automatically-update-stale-if-omniscope-runs-out-of-memory-when-updating-block-in-dm Mon, 18 Jul 2011 05:58:40 -0400 Alk 864@/discussions
To resolve this, I have to select "Update Stale" and the blocks will update, often resulting in a block further down the workflow to become stale, where I have to click "Update Stale" again and repeat this process 4-5 times to update the whole workflow.

It would be very convenient if Omniscope waits 5 seconds and runs the "Update Stale" automatically if there is a out of memory error when updating a block in DM - and to prevent an endless loop of this, stop and report an error after 3-5 attempts of updating stale blocks if Omniscope is still on the same block.]]>