what r transaction synchronistion
bugs
Synchronization in DSVM (distributed shared virtual memory)
process level instead of only at the memory access level.
idea in the context of transaction synchronization,
devising two-phase locking-based algorithms under two DSVM
with and without an underlying memory coherence system.
They compare the performances of the two algorithms and
argue that significant performance gain can potentially
result from bypassing memory coherence and supporting
process synchronization directly on distributed memory.
They also study the role of the optimistic algorithms in
transaction synchronization in DSVM.
Synchronization bugs are caused by physical phenomena which
cause the actual behavior of a chip to be different than
predicted according to the functional model. Traditionally,
verification methods such as dynamic simulation and model
checking use a synchronous model, whereas the actual
behavior is according to an asynchronous model. Because of
this, synchronization bugs are very hard to trace. Using a
model checker we were able to create a model closer to the
actual behavior, and retrace many synchronization bugs.
Because model checking allows us to introduce non-
determinism when checking a VLSI design, and because of its
ability to produce counter examples for specifications that
fail, we find that model checking is the ideal tool for
reproducing synchronization bugs.
| Is This Answer Correct ? | 1 Yes | 0 No |
What is maintenance testing?
What do you think is the perfect test management system for test service vendors like me?
1.WHY DO YOU GO FOR WHITE BOX TESTING,WHEN BLOCK BOX TESTING AVALIABLE? 2.WHY DO YOU MAINTAIN REPOSITERIES AND WHAT IS REPOSITORY?
which is the best institute for testing in hyd?
What is the common risk that leads to project failure?
What is affinity diagram?
What are the benefits of independent testing?
What is impact analysis? As a tester how will you do impact analysis in your project?
Explain inspection?
What is the difference between Testing and Code review?
Actually how many positive and negetive testcases will write for a module?
What is the average size of executables that you have created?