A common problem of multithreaded applications or separate applications accessing shared memory is concurrency control. Current applications usually use locking to access shared memory, but this has several well-known disadvantages like bad scalability or bad maintainability. As many developers will have experienced, it is an extremely tedious task to choose the right locking granularity (not too many, not too few) and to apply and release them in the right order to avoid deadlocks.
Search
About
You are currently browsing the Michel Weimerskirch weblog archives for the Articles and Papers category.
Latest
RSSArchives
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- January 2010
- December 2009
- November 2009
- October 2009
- July 2009
- April 2009
- January 2009
- December 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- December 2007
- October 2007
- September 2007
- August 2007
- September 2006
- June 2006
- May 2006
- April 2006
- December 2005
Categories
- Archive (5)
- Articles and Papers (1)
- Lëtzebuergesch (1)
- Music (4)
- Photos (3)
- Projects (8)
- Software (5)
- Spellchecker.lu (10)
- Stuff (7)
- Uncategorized (4)
- Web Development (5)
Search
Follow me on Twitter
- working on my own #symfony based CRM tool 2010/09/07
- @kriswallsmith You could talk about optimizing symfony applications (for speed, less memory, ...). That would be interesting. 2010/09/03
- I have just submitted my first iPhone app. It's built with #phonegap. 2010/09/03
