Browse by Tags

• performance

Using ReaderWriterLock part 3 (last in this set)
15 May 06 05:32 PM | ricom | 0 Comments   

Well I think it's raining ReaderWriterLocks this month! Jeff Richter has an article on MSDN that goes over a lot of the basics and some stuff that's a lot more than basic. And then there's Vance Morrison's March article on the subject as well. Lots of Read More...

Filed under: performance, locking

Using ReaderWriterLock part 2
12 May 06 12:31 PM | ricom | 5 Comments   

Well the trouble with simple samples like the one I provided in part 1 is that well... they're too simple. Some of the improvements that you can make in them won't work generally. But nonetheless I think there's some interesting discussion possibilities. Read More...

Filed under: performance, locking

Using ReaderWriterLock -- are you getting what you think you're getting?
05 May 06 11:51 AM | ricom | 14 Comments   

Oh boy, more locking problems for the weekend! Here's a more complicated lock that often gets used when it shouldn't and is avoided when it should be used. Like the other articles in this series I'll provide a bit of code and ask for comments, it's more Read More...

Filed under: performance, locking

Putting your synchronization at the correct level -- solution
03 May 06 10:42 AM | ricom | 13 Comments   

Of course when I say "solution", I really mean "my solution" because there's not really just one way to do this. But this is an approach I like and I'll go over why I like it. Recall the code from the original problem : (there was some very interesting Read More...

Filed under: performance, locking

Putting your synchronization at the correct level
01 May 06 11:43 AM | ricom | 33 Comments   

Continuing in what's turned into my series on locking advice, I have a new example for you of a typical problem that happens in class design. As usual I've simplified this almost to the point of being silly to illustrate the problem. Hopefully the crux Read More...

Filed under: performance, locking

Simplify your locking strategy -- simpler is better
28 April 06 03:29 PM | ricom | 18 Comments   

Well I didn't mean to but it seems I'm writing a series of articles on locking. Based on my last posting I got several requests for a simple example of a case that could be improved with simpler locking. Here's something of that ilk that's similar to Read More...

Filed under: performance, locking

Locking -- Isolation -- Unit of Work -- Performance -- Solution
26 April 06 10:33 PM | ricom | 7 Comments   

A few days ago I posted a concurrency problem for commentary and I got a very nice set of responses. Now I can't say that there is any answer to this problem that I would say is universally correct but there are some interesting observations that we can/should Read More...

Filed under: performance, locking

Locking -- Isolation -- Unit of Work -- Performance
24 April 06 07:54 PM | ricom | 11 Comments   

I've had a bit of a locking/threading theme in some of my recent postings so I thought I'd continue that with a little problem. Here's a (simplified) set of operations that is sort of an example of what you might need to do in a free threaded class. Let's Read More...

Filed under: performance, locking

Same Resource, Same Lock or else locking won't give you the protection you need
22 March 06 06:49 PM | ricom | 6 Comments   

I sometimes see funny locking patterns because there is a mental assumption that the lock keyword (via Monitor features of the runtime) automatically guards the contents of the locked region. This isn't the case. All that is guaranteed is that only one Read More...

Filed under: performance, locking