Talk:COMP 3000 Essay 2 2010 Question 5

From Soma-notes
Revision as of 12:37, 17 November 2010 by Myagi (talk | contribs)
Jump to navigation Jump to search

Maybe we can all add our names below so we know who's still in this course? --Myagi 12:38, 14 November 2010 (UTC)

Group members:

  • Michael Yagi
  • Nicolas Lessard
  • Julie Powers
  • Derek Langlois

Jeffrey Francom contacted me earlier so I know he is also still in the course. Now we are only waiting on Dustin Martin. Everyone has been accounted for. J powers 18:07, 15 November 2010 (UTC)

Just kicking things off. Feel free to make suggestions or change anything. --Myagi 11:36, 17 November 2010 (UTC)


Essay

Paper

The paper's title, authors, and their affiliations. Include a link to the paper and any particularly helpful supplementary information.

Background Concepts

Explain briefly the background concepts and ideas that your fellow classmates will need to know first in order to understand your assigned paper.
  • Execution Filters: Otherwise known as request filtering. Request filters allow you to inspect the request before and after the main logic is executed.
  • Hot Patches: "Hot patching is the application of patches without shutting down and restarting the system or the program concerned. This addresses problems related to unavailability of service provided by the system or the program. A patch that can be applied in this way is called a hot patch. Hot Patching
  • Hybrid Instrumentation Engine: Instrumentation refers to an ability to monitor or measure the level of a product's performance, to diagnose errors and writing trace information. Instrumentation Instrument programs can have low runtime overhead, but instrumentation has to be done at compile time. Dynamic instrumentation can update programs at runtime but incur high overhead. A hybrid instrumentation is an implementation of combined static and dynamic instrumentation.
  • Lock: "In computer science, a lock is a synchronization mechanism for enforcing limits on access to a resource in an environment where there are many threads of execution. Locks are one way of enforcing concurrency control policies." Lock
  • Mutex: Mutually Exclusive; Unable to be both true at the same time.

Research problem

What is the research problem being addressed by the paper? How does this problem relate to past related work?

Problem being addressed

With the rise of multiple core systems, multithreaded programs are often prone to race conditions. Races are hard to detect, test and debug. Due to the immaturity of current race detectors, this paper explains a new approach to race detection and work arounds through the use of LOOM.

Past related work

Two common solutions to fixing deployed races are software updates and hot patches. Software updates require restarts whereas hot patches applies patches to live systems. However, relying on conventional patches can lead to new errors and could be unsafe, due to a multithreaded applications complexity. Releasing a reliable patch takes time, but developers often resort to more efficient fixes rather than placing proper locks in the application due to performance or work pressure.

Contribution

What are the research contribution(s) of this work? Specifically, what are the key research results, and what do they mean? (What was implemented? Why is it any better than what came before?)

Compared to traditional solutions, LOOM differs in its approach to races fixes. It is designed to quickly develop safe, optimized, temporary workarounds while a concrete solution is developed.

Current solution expressed

LOOM is compiled with a developers application as a plugin and kept separate from the source code. Execution filters are written by the developer and synced with the source code to filter out any racy threads. Users can then download the filter and apply to the application while it is still live. LOOM is flexible in that developers can make tradeoffs in performance and reliability in their application in conjunction with LOOM. These can include making two code regions mutually exclusive even when accessing different objects or with extreme measures, making them run in single threaded mode. LOOM's hybrid instrumentation engine is used to reduce its overhead. The engine statically changes an applications binary to anticipate dynamic updates. Evaluation of LOOM was based on overhead, scalability, reliability, availability and timeliness. These were demonstrated using Apache and MySQL in conjunction with the multithreaded ApacheBench and SysBench, respectively.

Critique

What is good and not-so-good about this paper? You may discuss both the style and content; be sure to ground your discussion with specific references. Simple assertions that something is good or bad is not enough - you must explain why.

Good

  • The author stays focused on the thesis and writes relevant examples and data relating to the thesis to evaluate the overall product.
  • The thesis is very clear in the papers abstract and introduction, explaining that there is a satisfactory way to deal with race conditions through the use of LOOM as its approach in doing so.
  • The example races, particularly the MySQL example, makes very clear the use of execution filters, which is the focus of the thesis through the use of LOOM.
  • The conclusion mentions everything that was discussed in the body of the work in a very concise and clear manner.
  • The paper has good references, especially pertaining to concepts and vocabulary people might not be familiar with.

Not-So-Good

References

You will almost certainly have to refer to other resources; please cite these resources in the style of citation of the papers assigned (inlined numbered references). Place your bibliographic entries in this section.
Retrieved from "https://homeostasis.scs.carleton.ca/wiki/index.php?title=Talk:COMP_3000_Essay_2_2010_Question_5&oldid=5073"