Resolve Probing Performance!

Hi Von, 
OK, since you're on a a development machine the initial startup is probably not a concern.

The problem is that you're running a distributed application and this is the log from the server.  This log shows the server receiving the query at 16:32:53.  I can't tell when the query completes because I then see creation of a communication proxy, which should not be here.   Creation of that proxy is happening in the gap from 16:32:54 to 16:33:02, so I have to assume it's this causing the performance hit here.   Your application is creating a new EntityManager somewhere, likely in the custom query interceptor, which is causing this to happen.  Once we resolve this then we can see what else is happening with the first query and if that performance can be improved.

On the save, the server doesn't receive the save request until 16:33:15.  If your client application called SaveChanges at 16:33:11 then we need to understand what was happening between this call on the client and the time the request hit the server.  Do you have client-side event handlers in place?  What is your save interceptor doing?  What kind of validations are in place?  Additional diagnostics in your save interceptor may help here.

When you make a change to one property and then save the entity, the entire entity is still sent to the server.  Since you're saving only one entity it's unlikely the payload is large, but if that entity has byte arrays or large text fields then transmission could certainly be slower than you might expect.   Instance-level validation will also be performed on the entity during save processing, so check which verifiers will be running.

I should emphasize also that you'll always see delays (usually small) when the services first start, and upon the first query and save to hit the server.  This does mean that the unlucky user who experienced these will see some slowness, but not every user for every first query and save.  Once the BOS is humming along there will be no further initialization by either DevForce or EF.  

For further help, email to IdeaBladeSupportTrack, your client and server debug logs, the code from your custom login manager, the query and save interceptors, your EDMX, and any custom verifiers or buddy classes which add verifiers.  If it's easier, you can instead send a repro solution which exhibits these issues.

Kim