Hello,
in the httpd.conf the parameters MaxCGIJobs and MaxPersistentCGI are set to 1000 by default. This means, that no more than 1000 sessions can be started. Is this limitation founded on hard technical restrictions? I think, in our firm we need about 3000 sessions. Shall i set the values to 3000? Or shall i create 3 ProfoundUI instanced with 1000 session on each? Of course it would be more comfortable for me to have only one instance which can serve 3000 sessions.
If there is no technical reason, why is the limitation set to 1000, why does Profound Logic not set the default value on an very high value (e.g. 10000 or a *NOMAX value)?
When i change the MaxPersistentCGI value, i have to chance the MaxCGIJobs value also? Is it correct that both parameters always should have the same value?
Dieter
Why ist 1000 the default-value for MaxCGIJobs?
-
- Experienced User
- Posts: 122
- Joined: Tue May 22, 2012 6:45 am
- First Name: Dieter
- Last Name: Schröder
- Company Name: Ecclesia Holding GmbH
- State / Province: Outside Canada/USA
- Country: Germany
- Contact:
- David
- Profound Logic Staff Member
- Posts: 690
- Joined: Fri Jan 04, 2008 12:11 pm
- First Name: David
- Last Name: Russo
- Company Name: Profound Logic Software
- Contact:
Re: Why ist 1000 the default-value for MaxCGIJobs?
The 'MaxCGIJobs' and 'MaxPersistentCGI' are specified in a default configuration simply to avoid the default values for these, which are something like 40-50, I think.
The number 1000 was not chosen for any special reason.
If you need 3000 sessions, you can go ahead and set 'MaxPersistentCGI' to 3000. I would recommend setting 'MaxCGIJobs' a bit higher, though, as there are some 'shared' CGI jobs that are not tied to a particular session -- such as for widget SQL statements, file upload / download, etc.
These will be reused/shared across all of your users. I'd think you'd want to allow for another 3000 of these (worst case), so set up like this:
The number 1000 was not chosen for any special reason.
If you need 3000 sessions, you can go ahead and set 'MaxPersistentCGI' to 3000. I would recommend setting 'MaxCGIJobs' a bit higher, though, as there are some 'shared' CGI jobs that are not tied to a particular session -- such as for widget SQL statements, file upload / download, etc.
These will be reused/shared across all of your users. I'd think you'd want to allow for another 3000 of these (worst case), so set up like this:
Code: Select all
MaxPersistentCGI 3000
MaxCGIJobs 6000
Who is online
Users browsing this forum: No registered users and 3 guests