You are viewing limited content. For full access, please sign in.

Question

Question

Import Agent: Thread Count Limitations

Import Agent Version 11
Updated July 25
asked on July 25

I have an import server with 4 virtual cores and the thread count is set to 4 and parallel processing is enabled. This is an import dedicated server.

 

Is there any limitations for the Thread count option, can I up it to like 8 and is there any benefit having it that high or should it not go above the core count?

0 0

Replies

replied on July 25

If you're going to have import profiles run OCR, they'll likely be CPU-bound, so one per CPU is best. The other factors that might impact performance are the number of concurrently running profiles, disk and network traffic. Disk because Import Agent needs to move processed files around and network because these files need to make it to your Laserfiche Server.

So it's going to be a balancing act that probably will need a bit of experimentation to tweak just right. I'd start at 4 and see if performance is acceptable.

I wouldn't go past 15 is all profiles are using the same login to the repository.

3 0
replied on July 25

Awesome and thank you, in total there is a few servers all processing to the same repo with the same settings and core count for an initial migration. Right now its just 1-2 profiles with their own logins running with no OCR on each but these profiles each have about 3 Million records to pull in. Just looking to see if this can help give me even a small boost without causing issues

0 0
replied on July 25 • Show version history

If it helps provide a frame of reference, our main Import Agent instance is configured with 8 virtual processors and a thread count of 8.

We have 2 main profiles that usually pull in about 2,500 documents each per day, we do not run OCR on import (we do most OCR with the DCC).

The same server is also shared with our Quick Fields agent, which processes another 5,000 or so documents per day.

We've never had any major issues with Import Agent performance, and during past conversion processes we've had as many as 8 profiles running on that same server to bring in large batches of documents.

This is a bit anecdotal, but our experience made it seem like putting everything in one folder could also create a bottleneck. For bulk imports we started enabling more profiles with their own folders to spread the files out, and it did seem to make a substantial difference in throughput.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...