Jump to content

Mike O.

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by Mike O.

  1. 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
  2. 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
  3. 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
×
×
  • Create New...