Databases
StackOverflow2013
Postsdbo
POis it better performance wise to use the concrete type rather than the interface
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POis it better performance wise to use the concrete type rather than the interface
    primarykey
    data
    text
    <p>I have run into some rules (recommendations) to use concrete <code>List</code> and <code>Dictionary</code> rather than <code>IList</code> and <code>IDictionary</code>, given the sample tests that show accessing through the interface is quite a bit slower. For example, adding 10000 values to a list and then doing a <code>Count</code> on the list 1 billion times shows that doing it through an interface is 28 times slower then doing it through the concrete class. Ie, through the concrete class it takes 80ms, through the interface it takes 2800ms which shows how really slow it is through the interface. Given this would it be reasonable use the concrete class. Is there a reason why the interface is so much slower? (Probably more directed at someone who know more about the internals of .net).</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USpolkduran
    1. USuser455095
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POis it better performance wise to use the concrete type rather than the interface
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POis it better performance wise to use the concrete type rather than the interface
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POis it better performance wise to use the concrete type rather than the interface
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhat language has such miserable performance with interfaces?
      singulars
      1. POis it better performance wise to use the concrete type rather than the interface
      1. USdicroce
    2. COIList<int> ilst = lst; for (int i = 0; i < 10000; i++) { lst.Add(i); } int count = 0; GC.Collect(); for (int i = 0; i < 1000000000; i++) { count = lst.Count; }
      singulars
      1. POis it better performance wise to use the concrete type rather than the interface
      1. USuser455095
    3. COA performance difference of a factor 100 will seldom be seen. I doubt the correctness of your performance measurements. Can you show us your code?
      singulars
      1. POis it better performance wise to use the concrete type rather than the interface
      1. USSteven
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload