Maximum number of connections

[eelias]

Hi there,

 

There are some partners asking me about the ability of UNIGUI with multiple simultaneous connections.

 

One is saying that Delphi is based in the classes web.webreq and it cannot support more than 30 or so simultaneous connections in ISAPI, if you use it as WebBroker.

 

So, what is the real capabilities of Unigui, can it handle a thousand connections simultaneously ? (consider a perferct hardware for this).

 

Or somehow the request as serialized to be treated on Delphi side and sent back to outside?

 

thank you

 

Eduardo

[Sherzod]

Hi,

 

http://www.unigui.com/explore/matrix/#featurem

[eelias]

I am looking for more of a technical information.... This table can be seen as just commercial info.....

[Sherzod]

⁵ Actual maximum number of concurrent sessions is limited by system resources, application design, database engine and other factors.

[eelias]

so you are telling me that Unigui does not use Delphi´s WebBroker that has the limitation of 30 or so connection?

[Farshad Mohajeri]

Hi there,

 

There are some partners asking me about the ability of UNIGUI with multiple simultaneous connections.

 

One is saying that Delphi is based in the classes web.webreq and it cannot support more than 30 or so simultaneous connections in ISAPI, if you use it as WebBroker.

 

So, what is the real capabilities of Unigui, can it handle a thousand connections simultaneously ? (consider a perferct hardware for this).

 

Or somehow the request as serialized to be treated on Delphi side and sent back to outside?

 

thank you

 

Eduardo

 

Hi,

 

uniGUI is not based on Webreq or Webbroker.  It implements its own ISAPI handlers.

uniGUI can handle high number of incoming connections, as long as your app is able to server them and your hardware resources are enough.

Requests are not serialized in Delphi. They are processed in parallel.

There are parameters that limit the number of parallel requests in uniGUI. By default 50-100 is recommended for parallel requests. It is the same in IIS too.

 

For most of the applications the default value of 50 is the most optimal value, but it can be increased to 100 or more based on your application. In any case values above 200 are not recommended. The reason for this is that multi-threading performance of your system will not increase when number of running concurrent threads go above a certain threshold. On the contrary running too many threads in parallel may decrease multi-threading performance of your system, as CPU needs to switch between tasks many times per second. Hence the amount of time dedicated to task-switching can become too high, decreasing the time dedicated to perform the actual tasks.