Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Edit 2:</p> <p>I had another potential thought here:</p> <p>You mentioned that you are running on x64. I've tested this same issue on x86, and seen the same performance when using auto-properties vs. fields. However, if you look around on Connect and mailing list/forum posts, there are many references online to the fact that the x64 CLR's JIT is a different code base, and has very different performance characteristics to the x86 JIT. My guess is this is one place where x64 is still lagging behind.</p> <p>Also, FYI, the struct/method/etc thing fixed in .net 3.5sp1 was on the x86 side, and was the fact that method calls that took structs as a parameter would never be inlined on x86 prior to .net3.5sp1. That's pretty much irrelevant to this discussion on your system.</p> <hr> <p>Edit 3: </p> <p>Another thing: As to why XNA is using fields. I actually was at the Game Fest where they announced XNA. Rico Mariani gave a talk where he brought up many of the same points that are on his blog. It seems the XNA folks had similar ideas when they developed some of the core objects. See:</p> <p><a href="http://blogs.msdn.com/ricom/archive/2006/09/07/745085.aspx" rel="noreferrer">http://blogs.msdn.com/ricom/archive/2006/09/07/745085.aspx</a></p> <p>Particularly, check out point #2.</p> <hr> <p>As for why automatic properties are better than public fields:</p> <p>They allow you to change the implementation in v2 of your class, and add logic into the property get/set routines as needed, without changing your interface to your end users. This can have a profound effect on your ability to maintain your library and code over time.</p> <p>---- From original post - but discovered this wasn't the issue--------</p> <p>Were you running a release build <em>outside</em> of VS? That can be one explanation for why things aren't being optimized. Often, if you are running in VS, even an optimized release build, the VS host process disables many functions of the JIT. This can cause performance benchmarks to change.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhy are public fields faster than properties?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USReed Copsey
    1. USReed Copsey
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhy are public fields faster than properties?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    1. COYes, I've tried closing all instances of VS and running the .exe in the Release folder, but same result (although both versions are slightly faster outside VS). And yeah, that's a good reason to use properties even if you don't fill in the get/set at first :)
      singulars
      1. PO
      1. USJulianR
    2. COThe best usage cases for struct types are the ones which serve to bind a few variables together with duct tape (e.g. the coordinates of a point). If a struct is supposed accept any pair of integers and report them as X and Y, there isn't really any useful behavior a future version of the type could possibly add to X and Y property accessors without breaking things. Better to have a struct say what it is (an X field and a Y field), than keep it "secret".
      singulars
      1. PO
      1. USsupercat
 

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