I had the same problem with an Infragistics Grid. The time of loading was 25 times slower than the DataGridView. I found an option in the Infragistics grid

this.grid.DisplayLayout.LoadStyle = Infragistics.Win.UltraWinGrid.LoadStyle.LoadOnDemand;

By default, this option is set on PreloadRows. Now with the property set on LoadOnDemand, my grid loads in 600 ms.

So I advise you to search the same kind of option in the DevExpress Grid. It may help you

David

An example from my app: 1 Million row table containing production of individual pieces. I've just opened our transaction maintenance form and randomly selected a date range in 2006. The grids (DevExpress) filled in about 15 seconds with 20,000 rows. Each transaction row populates two different grids (within a tab control) and one of the grids has extensive DexExpress subtotals. Each grid contains about 20 columns. I opened the form in the Visual Studio IDE.

I think your issues are more in finding and presenting the required dataset to the BO you are using in the DevExpress grid.

Cheers, Peter

I don't think anyone is asking you to restrict your users My users frequently load tens of thousands of records into Infragistics grids and they don't see times that you are reporting.

The times you are reporting tell me that Infragistics is at least 8 times faster than Devexpress. Even though the thread we linked above relates to Infragistics grids I believe the same issue will also apply to Devexpress so I hope you read it. There is a MASSIVE difference in grid loading times for complex grids when running in the debugger and outside of it. With a F5 run in Visual Studio (i.e. running in the debugger), I can see 3 mins 20 seconds to load 15000 records. When I run without the debugger (CTRL+F5) this drops to 7 seconds - this is also the time users will see as, obviously, they don't run the debugger

A complex grid (like Infragistics or Devexpress) will never be as fast as the simpler DataGridView as there is a performance overhead for all those nice powerful features. However, I know for a fact that Infragistics/SF running outside of the debugger is not taking the times you are reporting so this must be a Devexpress/environment problem. I can also assure you, for good or bad, some users will pull in far more than 30,000 records and could do this several times over in the time you are waiting for one grid to load.

I really hope you have tried running CTRL+F5 - the other user hadn't and reduced a 5 minute loading time down to 20 seconds just by doing this one action.

Aaron

Just to reiterate here.  This is not an issue with StrataFrame.  For the record, in our medical application, we use the Infragistics grid.  In certain conditions, we may populate that grid with more than 6000 records.  So this framework and grids are more than capable of performing fast.

I also know that this is not an issue with the BBS as this is another test that we have just run due to some of these posts and proven that there are no performance issues in this regard.  It could be, however, that due to the nature of the DevExpress and Infragistics grids, that a certain property, configuration, etc. could be causing for evaluations that are really necessary.  The proof in this case, that is not the BBS or SF, is like you said, it is 30 times faster using the same SF controls on a DataGridView, but when you do the same thing on a DevExpress grid, things slow down.  I know for a fact, as we have a lot of users that use DevExpress as well as Infragistics, that these grids can perform very fast with large records sets using StrataFrame. 

As I've stated that we have large amount of data. User may query between two or more months and gets thousands of records. We can not restrict them.

Again, The question is related to Devexpress Grid performance. (May be BBS related issue).

Test and easily see the results. If you have better results then I will think this is related with Devexpress and my environment settings.

Until we reach the better test results, this is SF related (SF-Devexpress relation).

I think this thread contains plenty of performance times and suggestions:- http://forum.strataframe.net/Topic17575-7-1.aspx

Aaron

I have also extended the test by selecting one column and set AllowFilter to false.

This is very critical point for us. We have large DB in our customer. We can not deploy the forms.

My test is based on local PC. (SQL Server is running on local machine and no network traffic.)

Please share your test results with us.

This is definitely an issue when running in debugger mode in Visual Studio. Instead of running your application by pressing F5, try CTRL+F5 as that will run your application without the debugger - you should see a drastic improvement in performance.

Aaron

This is common with 3rd party grids when running through the F5 debug environment.  This has nothing to do with SF.

There is a big difference. I wonder, What is the reason behind ? Is it known issue ?

Everyone tests this condition easily.