Home/ Questions/Q 311737
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T07:57:08+00:00

I noticed that disposing and re-creating a DataContext is way faster than refreshing it

  • 0

I noticed that disposing and re-creating a DataContext is way faster than refreshing it with RefreshMode.OverwriteCurrentValues, which should effectively be the same.

While this causes my application to spike at 100% CPU for several seconds

dbc.Refresh(RefreshMode.OverwriteCurrentValues, dbc.Property);

the following code doesn’t even eat up 50% of CPU and takes approximately a single second:

dbc.Dispose();
dbc = new PropertyManagementDataContext();

while also overwriting all my local changes and just updating my local data from the DB. Or did I overlook something?

Is there any danger to dispose and re-create the DataContext in order to get the latest data from the Database?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Refresh() is actually round-tripping to the database. Disposing and recreating the context is using locally cached connection info. This will be faster.

    Edit:
    Also, according to the docs you’re probably using Refresh() for the wrong reason. See the remark toward the bottom.

    • 0