Performance Concurrency/Scalability - Let's Chat About It! - AJAX / Silverlight applications framework

Welcome Register | | Send to friend | Sales | Download

DEVELOP WEB APPLICATIONS WITH THE BEST AJAX FRAMEWORK.

CREATE LINE OF BUSINESS SILVERLIGHT APPLICATIONS IN NO TIME.

EVERY THING YOU NEED TO START DEVELOPING WITH VISUAL WEBGUI.

SEE VISUAL WEBGUI SHOW CASES FROM AROUND THE WORLD.

ALL THE RESOURCES YOU NEED TO START BUILDING VISUAL WEBGUI APPLICATIONS TODAY.

SHARE AND FIND VISUAL WEBGUI RESOURCES.

TALK WITH OTHER VISUAL WEBGUI DEVELOPERS.

Forums

SAP has chosen Visual WebGui for strategic web application, Mr. Saar of SAP explains why in an interview with with Jeremy Geelan at AJAX World.

Click on the video image to watch

Search Forum Home

Forum General Visual ... Let's Chat Abou... Performance Concurrency/Scalability

11/13/2008 7:32 AM

	jworthy
1 posts

Performance Concurrency/Scalability

I currently support a large asp.net application and am interested in converting it to WebGUI. Faster development and a richer UI are the primary reasons I'm considering the switch. My concern is performance. My current app has over 140 aspx pages and will eventually be accessed over SSL by 250 locations and between 750-1000 users. Concurrent usage may average 100 or fewer (active sessions), but peak times may see 200-300 or more. This is a business application and most of the time is spent adding, editing and deleting data--lots of forms, lots of grids. Does anyone have any real experience with this size of application? Also, can anyone speak to the concurrency issues generally and then specifically regarding the impact of session state and scalability?

Thanks for your help.
--John

11/18/2008 1:22 AM

	ori.cohen
1148 posts

Re: Performance Concurrency/Scalability

Hello John!

Welcome to Visual WebGui!

I'm glad to hear that you are seriously considering converting your applications to Visual WebGui.
Our system is designed to be very scalable and built from the ground-up to support a vast amount of concurrent users per-machine in enterprise applications.

A single server can hold between 200-400 concurrent users depending mostly on the machine.
* VWG almost eliminates the limitation in terms of CPU usage due to the fact that it does not construct and destruct objects/controls rapidly as ASP.NET.
* VWG consumes only a small amount memory on the server more than ASP.NET (between 1-10Kb per user) in order to keep a local copy of objects model alive on the server when the application is running.
* When using server capabilities extensions such as communication server, one server will support fewer users since it handles requests more tightly.
* Your BL and DL can enforce you to deploy on more than one server due to other load limitations (non-VWG considerations).

If you have any more questions or issues that need to be clarified please reply to this post, and we will be more than happy to assist you.

Regards,

Ori Cohen
The Visual WebGui team