[Archivesspace_Users_Group] Indexer Thread Counts
Joshua D. Shaw
Joshua.D.Shaw at dartmouth.edu
Tue Jan 5 17:43:00 EST 2021
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of James Bullen <james at hudmol.com>
Sent: Tuesday, January 5, 2021 5:19 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Indexer Thread Counts
1) Yes, additive
2) The public index was considered less time critical
There’s no problem with increasing the PUI indexer thread count if you have the resources.
On Jan 6, 2021, at 1:41 AM, Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu<mailto:Joshua.D.Shaw at dartmouth.edu>> wrote:
Couple of questions about indexer thread counts
1) Before I dive too deeply into the code to figure this out, I'm wondering if anyone knows if the setting for AppConfig[:pui_indexer_thread_count] is counted as part of AppConfig[:indexer_thread_count] or if its additive? IE if the stock config setting amounts to 5 threads (4+1) or 4 threads.
2) Is there a reason that the PUI indexer thread count is set so much lower than the staff side?
I'm thinking of upping the PUI thread count to something closer to the staff side since we have the cores to support that, but I'm wondering if there might be some unforeseen negative side effects.
Joshua Shaw (he, him)
Rauner Special Collections Library & Digital Library Technologies Group
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Archivesspace_Users_Group