lock keyword in C#

by

When should the lock be used?

A lock should be used to protect shared resources in multithreaded code. Not for anything else.

But is it necessary when the application does not spin off any other threads?

Absolutely not. It’s just a time waster. However do be sure that you’re not implicitly using system threads. For example if you use asynchronous I/O you may receive callbacks from a random thread, not your original thread.

Is there performance issues with using lock?

Yes. They’re not very big in a single-threaded application, but why make calls you don’t need?

…if that is a good design pattern to follow in the future[?]

Locking everything willy-nilly is a terrible design pattern. If your code is cluttered with random locking and then you do decide to use a background thread for some work, you’re likely to run into deadlocks. Sharing a resource between multiple threads requires careful design, and the more you can isolate the tricky part, the better.

More Related Contents:

  1. Why is lock(this) {…} bad?
  2. Volatile vs. Interlocked vs. lock
  3. Concurrent HashSet in .NET Framework?
  4. Asynchronous locking based on a key
  5. Re-entrant locks in C#
  6. Is Task.Factory.StartNew() guaranteed to use another thread than the calling thread?
  7. Is it OK to use a string as a lock object?
  8. Does a locked object stay locked if an exception occurs inside it?
  9. How expensive is the lock statement?
  10. Monitor vs lock
  11. What are the differences between various threading synchronization options in C#?
  12. Do I need to lock or mark as volatile when accessing a simple boolean flag in C#?
  13. Raise Events in .NET on the main UI thread
  14. C# manual lock/unlock
  15. Throw a NullReferenceException while calling the set_item method of a Dictionary object in a multi-threading scenario
  16. Why does the lock object have to be static?
  17. When is ReaderWriterLockSlim better than a simple lock?
  18. Cross-Process Locking in C#
  19. Why is it a bad practice to lock the object we are going to change?
  20. Guidelines of when to use locking
  21. If async-await doesn’t create any additional threads, then how does it make applications responsive?
  22. reference assignment is atomic so why is Interlocked.Exchange(ref Object, Object) needed?
  23. Proper way to implement a never ending task. (Timers vs Task)
  24. A way of casting a base type to a derived type
  25. Why CancellationToken is separate from CancellationTokenSource?
  26. How to correctly read an Interlocked.Increment’ed int field?
  27. Async WebApi Thread.CurrentCulture
  28. Populating a DataGridView with Text and ProgressBars
  29. When exactly does .NET Monitor go to kernel-mode?
  30. Is a bool read/write atomic in C#

Leave a Comment