Question About "processExecutor" and "timeoutMinutes" in settings.yml

[thiagoor-cpu]

Hello, I have a quick question regarding the processExecutor and timeoutMinutes values in settings.yml.

For SessionLimit, is the limit applied per user or per server/deployment? For example, if I set pdfToHtmlSessionLimit: 1 and have 100 users on my Stirling-PDF server, does this mean only one user can use pdftohtml at a time?

Additionally, what happens when the timeoutMinutes value is exceeded? If pdfToHtmltimeoutMinutes is set to 20, does the system return an error message to the user after 20 minutes?

Also, can I change this values??

Or am I misunderstanding the purpose of processExecutor and timeoutMinutes entirely?

Thanks in advance for clarifying!

[Frooodle]

per server deployment, its the total amount of executions that can be running on that server

does the system return an error message to the user after 20 minutes?
Yes

and yes you can edit the settings.yml for that purpose

[thiagoor-cpu]

So, if I have this server deployment for 100 users, assuming my hardware is capable, should I set the values to something like this to make sure no one stay idle waiting to be served?:

libreOfficeSessionLimit: 100
pdfToHtmlSessionLimit: 100
ocrMyPdfSessionLimit: 100
pythonOpenCvSessionLimit: 100
ghostScriptSessionLimit: 100
weasyPrintSessionLimit: 100
installAppSessionLimit: 100
calibreSessionLimit: 100
qpdfSessionLimit: 100
tesseractSessionLimit: 100

libreOfficetimeoutMinutes: 120
pdfToHtmltimeoutMinutes: 120
pythonOpenCvtimeoutMinutes: 120
ghostScripttimeoutMinutes: 120
weasyPrinttimeoutMinutes: 120
installApptimeoutMinutes: 120
calibretimeoutMinutes: 120
tesseractTimeoutMinutes: 120

I mean, the value limit of this fields is what my hardware is capable right? or the "subsystems" of StirlingPDF also have a limit ?

Also, the user get a message if the server is already at the limit and he need to wait to be served OR he need to enter again in the page and try again manually the process to get served?

Thanks!

[Frooodle]

We currently dont inform the user of any queue they might be in, this is a enhancement we want to add but isn't current there

as for the limits, there is no limit on stirling PDF systems it would instead be on your server itself
But certainly I wouldn't set it to be total user count, the likely hood of all 100 users converting a file at the same time is drastically low, and generally speaking a system wouldn't be able to handle such a load (unless you implemented load balances and multiple distrobuted systems)

[thiagoor-cpu]

I understand, is there any way to have some kind of statistics about number of users using the system in general or at the same time or something like that to be able to size this parameters correctly?

Thanks!

[Frooodle]

Not currently, we track total website usage such as total requests sent since last restart etc, but not total concurrent users at a time etc

[thiagoor-cpu]

Ok, thanks!