Quantcast
Channel: Entity Framework
Viewing all articles
Browse latest Browse all 10318

Edited Task: Perf: Investigate impact of using server side generated Guid as the primary key of a column [222]

$
0
0
"ADO.NET Entity Framework 4.0 introduces support for server side generated Guid as the primary key of a row. The FAQ for EF 1.0 warns against client side generated Guids as it informs they will result in inefficient index maintenance within Sql Server.

I've got a program which a number of times looks up an object (i.e. a row), analyses it, and synthesizes new objects (i.e. new rows).

My machine has four cores and 25 GB of RAM.

When I run this program using client side generated Guids the program takes 59 minutes to run. In this case the Sql Server 2008 takes approximately 5% to 10% of the processing power.

When I run this program using server side generated Guids (no other changes are made) the program takes 2 hours and 37 minutes to run. In this case the Sql Server 2008 takes approximately 50% of the processing power.

I've tried to run the tests multiple times, at every run the difference is the same.

This looks very strange. I would rather assume the server side generated Guid variant should take at most the amount of time which the client side variant takes.

Can't you take a look into this, please?"

This item was migrated from the DevDiv work item tracking system [ID=6271].

This work item originated from connect.microsoft.com. A member of the EF team at Microsoft should close the related Connect issue when closing this work item.


Viewing all articles
Browse latest Browse all 10318

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>