Visokio Forums

mburgess · February 10, 2012 4:54AM

hi

i am aware visokio creates temporary files on the hard drive equivalent to the memory in use by the iok file for the individual processes within it

my question is we have a PC with a small C (free space 5GB), but a much bigger D (free space 50GB)

i have had the message that action cannot be completed because not enough disk space from scheduler

will this be because 5GB is not enough or 55GB is not enough (memory in use by javaw.exe was just over 50GB just before i got the message

my question is essentially can we increase the D drive or add more hard drive space internally for visokio to use or does it need to be on the C drive

thanks
Matt

steve · February 10, 2012 11:50AM

Currently the cache defaults to a folder in the system temp folder, typically "C:\Users\name\AppData\Local\Temp\vo_bindiskcache3".

Its size is automatically determined on starting Omniscope to be the lesser of 20% of the free space on that disk and 5gb.

So in your case you'd be limited to a 1gb cache - too small for large data files; you will find that blocks will need to refresh from source too often.

You can't currently customise this through the UI. Instead you need to edit the installconfig.properties file and add the following JVM arguments:

binaryDiskCacheLimitMb: Disable automatic sizing and specify a fixed size in MB; you must ensure there is enough disk space.
binaryDiskCacheLocation: Path to custom location

Each argument must be prefixed "-D". For example, you might want to configure yours as:

ADDITIONAL_JVM_ARGS=-DbinaryDiskCacheLimitMb=20000 -DbinaryDiskCacheLocation="D:\omniscope_cache"

This results in a 20gb cache on the D drive.

Due to a fault which has today been fixed, these options won't work in your version - you will need to update to tonight's build, 2.7 b239 or later, to get the fix.

Note that one idea we're considering is allowing you to specify a fixed cache location on a per-project basis. So in a given IOK file DataManager model, you could choose to have a cache folder adjacent to the IOK file. This would prevent other models from flushing data out of the first model's cache; currently data is flushed from the cache when it fills up with other more recently accessed data.

sved · February 13, 2012 3:04AM

Hello Steve,
Version 2.7 b239 is not available on your website, I've tried to download it, but latest available on website is Omniscope 2.7 Alpha b235 for Windows(9 Feb 2012) , where can I found latest version, recommended by you?
Thanks.

steve · February 13, 2012 4:47AM

I'm afraid the daily builds failed tests at the end of last week. A new build will be up today. Check back in 2 hours.

steve · February 17, 2012 5:31AM

Sved, Matt - did you customise the cache? If so, did it help performance?

mburgess · February 17, 2012 9:57AM

yes, thanks - but when we had run out of disk space i deleted the cache & tried to re-start, it didn't work, i ended up re-booting as obviously it hadnt removed the cache (aware scheduler clears this, but not aware if there is an option anywhere in omniscope itself)

anyway - completed what i needed to do.

Visokio Forums

Welcome!

Categories