cats
jamesalleniwd
shuming
xiaohai
sunnylovey
adrienbrody
normancohn
daniellevan
rerqr
iaiyhadlda
habeb1
addisonjame01
yasmine1101
dellsony
jacobsebastian
toponscom
pinaldave
akkushaus
lapss321
Lenovo13
http://ozziemedessql.blog...
mayluobatty
ashishgilhotra
abcdee
AdaTheDev
lauriesteve
http://ghemant.myopenid.com/
&size=small&root=no¬humb=http://SqlServerKudos.com/Assets/Images/pg-preview-na.jpg)
Two things that people tell you about Entity framework performance are, use the Compiled Queryies and potentially remove tracking when its not needed. You can achieve this by using the CompiledQuery.Compile function to obtain a function that is your compiled query and to set the MergeOption of the relevant entities on the ObjectContext.
I've just finished banging my head against a wall when trying to assess the performance of these together.
This was my simple code. Create a static readonly function that is the compiled query and then in by test function checking the status of a check box to set the MergeOption to MergeOption.NoTracking.
sa
No comments yet, be the first one to post comment.