Search the Community
Showing results for tags 'memory'.
This might be a bit of a first world problem, but it has frustrated me a few times so I figured I may as well put my hand up. I run Intella on workstations with 64, 128 and 256 gigabytes of RAM. I find the slider to set the memory allocation for the application and for the crawlers is completely fine on the machine with 64, but for 128 and especially 256, I find each step of the slider is too "coarse" - for example I may want to set it to 8GB per crawler and the options I get are 7.77 or 8.25 (not exact examples but you get the idea). I say it's a first world problem because I'm sure ultimately it may not matter much, it's just not as precise as I would like. Similar to the manual crawler setting where there is an editable text box, I would appreciate an editable text box for the memory options, so I can set the exact amount of memory I want. I wouldn't get rid of the slider altogether, just let both be an option? I may be getting a "proper" server with 512GB (or even more memory!) in the future, so I anticipate the issue will compound further with more installed memory.
Intella 2.3 lets the user specify crawler resources to be used. This is good and bad. Our feature requests: - Add back the ability to configure the number of crawlers and crawler memory allocation to the inj config files. - Add the option / checkbox in the case config to specify that the Intella installation-specific limits should be used for processing this case. - Use the crawler and memory allocation specified in the config files as an upper limit to prevent over-allocation of resources. Background: In our team we have several people running Intella cases on system with differing HW specs. A crawler config that might be perfectly fine for one system will bring down another system to its knees, crashing not only the running Intella processing job, but also any other task that might have been running on this system.
Information can be found under: https://support.vound-software.com/#knowledge_base/1/locale/en-us/answer/71/