Jump to content

Search the Community

Showing results for tags 'processing'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Technical Support
    • General Technical Information
    • Intella 10/100/250/Pro/Team
    • Intella Connect/Node
    • Wishlist
  • News and announcements
    • Announcements
  • Talking Tech with Vound
    • Webinars

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 3 results

  1. 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.
  2. Hi, There are a few tasks, like Hreading and AI Coding that are very machine memory consuming. As those are background tasks, they use the current Intella Connect server memory and processor to ran. It will be verry nice if we could use another machine to perform this kind of tasks, like a NODE machine instead the current Connect Server. TKS Delson
  3. Hello, I currently have an OST that is processing in 2.0.1 and seems to have stalled out. It spent about 2 hours actively processing about 550,000 items as I would expect, but since then, it has elapsed 16 hours with no additional items processed. Has this been encountered before and is it a known issue? Is it a bad/corrupt OST? Or am I just being impatient and there really isn't an issue? For an environment baseline, my machine has 32GBs RAM, 8 core CPU, 4 active crawlers, 2 GB memory per crawler (set in the ini file to fix a previous issue), and I have indexed PSTs/OSTs larger than this 31GB one perfectly fine. Any thoughts or suggestions appreciated. Thanks
×
×
  • Create New...