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

Question

Question

Increase Quick Fields Speed

Quick Fields
Updated July 27, 2023
asked on July 25, 2023

Not to brag or anything, but I've got Quick Fields running on an over-powered VM (6CPUs, 32GB of RAM), and it never seems to run at more than 14% to 16%.  

I'm dealing with multiple large batches of files (1200 to 1500 records, 2400 to 3600 pages), and I'd like to make better use of my compute.  Any ideas?  

I can only set the "Simultaneous Sessions" to 2, despite having 6 CPUs.   But when I watch the Task Manager, I don't see anything that would indicate there are two sessions of anything running, only ever one session (assuming "Batch Processor Container" is a session).  

0 0

Replies

replied on July 25, 2023

Quick Fields is a 32-bit app, so it's subject to memory limits of 32-bit apps. Traditionally, Quick Fields was not memory-bound, but the OCR process only uses one CPU, so that is a limitation. Since a lot of Quick Fields' activity is dealing with image files, a faster disk may result in better performance.

Simultaneous sessions is used when multiple sessions are scheduled in Quick Fields Agent at the same time or a second one would start while another one is still running. If your sessions are shortlived or scheduled far enough apart, that setting is irrelevant.

If you're only running one session at a time, the usage you're seeing on your machine is pretty much what is expected.

1 0
replied on July 26, 2023

Thanks for the quick response.  Am I doing this wrong, then?  Should I be re-doing these Quick Fields as Workflows?  

The thing is - the OCR completes relatively quickly, but the processing of the documents goes on for a lot longer after that.  I was hoping to increase that processing time.  And my sessions aren't short lived currently.  Normally they are, but with the current batch of files the sessions can run all night.  We're talking about 39000 records, which are each 2 to 6 pages long.  300 to 1600 records per file.

 

0 0
replied on July 27, 2023

Those are kinda hard questions to answer without knowing what the session is doing.

If you're reprocessing existing documents, Workflow may be faster. If you are using Quick Fields to break a big batch into documents, then Workflow really can't do that.

All these batches need to go through the same session though to get sliced and diced into documents, right? Sifting through documents could be processing intensive too, depending on the number of document classes and processes used.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...