[How scalable is UniGui?]

State data are not limited to visual controls only. All user variables, Forms, data modules, DataSets, data connections, other non-visual components and etc. all together build a very complex state for current session which can only be kept inside memory. While more memory usage is a disadvantage here, there is a big advantage here in favor of stateful apps. uniGUI apps consume much less CPU and bandwidth usage compared to a stateless application. In a stateless application state info should travel back and forth between server and client. Each time a request is received session should be built using these state info which highly increases CPU and bandwidth usage. In a UniGUI app each Ajax calls send as few data packets as possible. There is no repeated traffic or state data inside an Ajax request packet.

 

I've seen ASP.NET applications with view state streams in magnitude of tens of KB which travels back and forth each time user sends a new request.

 

As they say, "proof is in the pudding".

 

Someone is going to have to stress test an application with Unigui on a webserver to see how many connections it can support and how much CPU and memory is needed for each connection. There is an excellent stress test software called StresStimulus Web Load Testing that works with Fiddler (both are free). They will show you in real time the memory and pageviews/sec etc. using only local machines. This is a "must do" BEFORE releasing a webserver into the wild.

 

Mike

[How scalable is UniGui?]

Farshad,

Thanks for the detailed response.

 

I don't understand why the server is using actual controls to store the state instead of using a simple TList or JSON array to handle all of the session data.

 

Mike

[How scalable is UniGui?]

I haven't used uniGui but before I get my hopes up, I'd like to know if it can scale.

 

For example.

 

How many concurrent users can a web server support at a time? 10? 50? 100? 500? How much memory does it consume per connection?

Is it stateless?

How many page views per second can it produce (excluding db access times)?

Does it have page caching?

Will it run on a server farm? For example. Can I have 10 web servers all connected to a central database server? And will the session data be centrally located? Or is the session data stored on the web server that initiated the session?

 

TIA

Mike