Performance and concurrent access

[landofdreams]

Hi,

I've been using SmartClient from one and a half years ago and I think it's a great platform to develop cutting edge web 2.0 applications. We rarely care about the concurrency and performance issues because our almost SmartClient applications are deployed in the intranet instead the public internet. If we want to create an internet application, what we need to pay attation to and how to enhance the performance? For example, the application must support a lot of users to access in the same time and the application should be able to handle a number of HTTP requests as quickly as possible?


In my opinion,SmartClient is a heavyweight framework compared with such so-called lightweight framework(Ext/jQuery,not include Dojo). And, the class system is necessary and helpful but it was too large therefore the performance will be a potential problem. I heared a few complaints from my colleagues and I'm wondering about the performance whether can fit the requirements.


Here are two specific problems:
1. first loading speed is slow(too large library?).
2. how to write code taht support concurrent access(I mean the server-side implementation).


Could you please give me some advice? I really have not had any experience like above.
Many thanks.

[Isomorphic]

Hi landofdreams,

First, a couple of misconceptions:

1. SmartClient is used in several major consumer-facing applications, including Intuit Quickbooks Online

2. Final SmartClient-based applications are usually more compact than applications built with smaller frameworks that deliver less functionality, because you start with a smaller framework but end up writing 2-5 times as much application code.

3. After initial download, SmartClient uses far less bandwidth than other frameworks because of sophisticated support for data caching and local sorting and filtering.

As far as advice for initial load performance, everything is covered under the Network Performance module's documentation.

When all these techniques are correctly applied, most sites are able to create a user experience where the user never waits for the framework to download. SmartClient.com itself is an example of this - the home page loads immediately, SmartClient begins downloading in the background, and the SmartClient Feature Explorer - which is far larger than typical applications - is ready to run when the "Explore" button appears.

As far as concurrency - do you have any particular issues in mind? There is nothing special about how you need to write server code for a SmartClient-based application vs an application based on any other client-side technology, in fact, SmartClient makes things easier with built-in support for detecting edits of stale data via dsRequest.oldValues (sometimes called the "long transaction" technique).

[zabedah]

what is smart client performance tuning

hi..

here i have a question
can u tell me the smart client performance tuning?
and tell me the benefit of smart client as well.

i hope that somebody reply my quesion as soon as possible
;)