I am always reluctant to use Netadvantage for ASP.NET controls when there already exist the same controls in VS2005 (i.e.: gridview, panel, tab). Although Infragistics controls are easier to use and has plenty of formatting options, the load that these controls add (JavaScript code in the resource file and styling images) push me away. I am not sure exactly how much it would increase the loading time or it would be noticeable for the user. I hope I am wrong
As I'm sure you've come to realize, software development is a constant tradeoff. Add more functionality, and performance takes a hit. In the new generation of web applications, end users have come to expect a rich experience, and that doesn't come for free. In many cases the performance hit is negligable, but there's always going to be a 'best case', where the feature-less will be faster than the feature-laden.
Here are a few things to think about.
Using AJAX techniques, you can break through performance barriers that were impossible to break through in the past. For example, you can use Virtual LoadOnDemand for the WebGrid to bind to millions of records, and have the performance of a grid with only 10 rows in it. Rich editing is made possibe using masked editors, and can be done without annoying postbacks to "enter edit mode". Paging can be done asynchronously, and the paging mechanism is built into the grid. There's an entire client-side API that you can use to program against any of the Infragistics controls without having to postback. Leveraging these aspects will enable you to create an application where the user can be more productive, and have a good experience.
Here are a couple of additional points to think about when dealing when any web application.
All script and css files are cached by both your webserver and the client browser. The client will only have to wait while the script is downloaded the first time they visit the site (unless they clear their cache).
Turning on GZIP compression on your WebServer can shrink the js files down quite a bit.
Also, you may have read in the beta forums that we're working on a new framework for our controls called "Aikido" One of the goals of this framework is to minimize the difference between "feature" and "performance". We want to deliver the features with the performance, and that's what we're focusing on.
I hope this helps,
-Tony
Hello,
We are using NetAdvantage for .NET+WPF 2007 Vol 3, the question that keeps coming up and I am looking for documentation on, is: Does NetAdvantage need to load, JavaScript or ActiveX controls to the client?
Can you point me in the right direction?
NetAdvantage for ASP.NET controls use JavaScript for client-side behaviors. Thus, they require JavaScript to be enabled on the client machine, but not ActiveX.
@Tony you forgot to mention a "HUGE" speed increase that you brought to my attention months ago when using app stylist and that is to rename the css stuff to a short name so instead of Office2007Blue rename it (and inside) to ob will cut down huge amounts on the overhead...
And to the OP gzip compression on IIS is great and if should be used "if you can" another way to go is to use Port80's Software which i use on some really intensive apps its fairly cheap and works well...
Link to port 80: http://www.port80software.com/products/httpzip/
Hi to all,
my programming team is currently evaluating the 2008 ASP.NET 2.X suite. After reading some of the forum discussions in regards to the poor performance of the webgrid I'm wondering if buying 10 licences is a good choice. For us, the application should respond quickly enough in order to keep the user experience excellent.
I would like to hear from your experience....since this is why a forum exist....to share our experiences....
The curent situation in our testing (using the demo version) is not acceptable. The webgrid is very slow in IE using a data set with less than 1000 records. Our current ASP application deal with close to 100k records....
Thanks in advance
Nicolas Monge
Project Manager, 20-20 Technologies
Hello Infragistics team,
I'm sure you will read this post....Could you please let me know if the performance problems of the webgrid have been corrected in the latest hotfix?
I use the Infragistics ASP.NET controls with 3 of my clients and the performance has been good. There are so many other factors that go into how the webgrid will perform. Client bandwidth, method of their internet connection, server load (includes RAM, server processes, and users), sql usage, and the amount of data being pulled out at once. There are so many factors that can affect performance of any ASP.NET application. Each of the clients that I have active projects for that include web development projects have differences in how their network connections and server configurations are set up. When developing you have to take that into account and develop your solution accordingly.
Infragistics provides interfaces for helping with these variables. For example, I have one client that needed to pull a large amount of records like yours, and to handle that much data on their small business bandwidth I had to make use of load-on-demand to push more rows only when the user needs it. With the webgrid control it makes this type of feature super easy to implement and not having to spend weeks developing the same solution keeps the client happy and myself available to work on further parts of the project. Infragistics knows that their ASP.NET controls aren't all they could be, and even so they are still saving my clients lots of money because it's less for me to code out like I use to.
I use Infragistics NetAdvantage for .NET which covers both the ASP.NET and Win Forms sides every day, and I'd recommend them to any developer.
If you are having a problem with 1000 records then something is wrong with your code and/or database.
Huge datasets can cause problems with "ANY" control, this isn't because of IG but is because of a combination of things including Database (indexes, subQueries and a shlew of other problems), WebBrowser, Compression, and Internet Connections.
When dealing with large datasets (in any application) you HAVE to take into consideration the database pulling 100k records in MSSQL "even with indexes" takes a bit (and yes we are talking mili-seconds and seconds) here but in my world that is an eternity... So given that...
Might I suggest (any control you use) implement custom pulls and caching and while IG has made this extremly easy with LoadOnDemand and Custom Paging you cannot expect ANY control to handle all this stuff for you and you will have this problem with ALL controls even the asp.net datagrid it is just a fact of life...
In IG you can grab the server side event and load "sets" of data at a time which is how I am able to handle 1mill+ records using web and wingrids with no performance problems and the reason is I cache the data into a per userDB and the grids pull from that (easier if it isn't a per user level) and then when the grid tells me they are paging to > X i pull the next set and stuff it into the userDB etc.