Concurrency Coordination in a Locally Distributed Database System
1979
- 110Usage
Metric Options: CountsSelecting the 1-year or 3-year option will change the metrics count to percentiles, illustrating how an article or review compares to other articles or reviews within the selected time period in the same journal. Selecting the 1-year option compares the metrics against other articles/reviews that were also published in the same calendar year. Selecting the 3-year option compares the metrics against other articles/reviews that were also published in the same calendar year plus the two years prior.
Example: if you select the 1-year option for an article published in 2019 and a metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019. If you select the 3-year option for the same article published in 2019 and the metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019, 2018 and 2017.
Citation Benchmarking is provided by Scopus and SciVal and is different from the metrics context provided by PlumX Metrics.
Example: if you select the 1-year option for an article published in 2019 and a metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019. If you select the 3-year option for the same article published in 2019 and the metric category shows 90%, that means that the article or review is performing better than 90% of the other articles/reviews published in that journal in 2019, 2018 and 2017.
Citation Benchmarking is provided by Scopus and SciVal and is different from the metrics context provided by PlumX Metrics.
Metrics Details
- Usage110
- Downloads106
- Abstract Views4
Report Description
A pipelined architecture for a locally distributed database system is proposed along with a simple concurrency coordination mechanism. The approach is based on the idea of serializing transaction processing throughout the database. The scheme is shown to require few coordination messages, to be deadlock free, to preserve database consistency, and to support recovery. Several performance related issues are also discussed.
Bibliographic Details
https://openscholarship.wustl.edu/cse_research/873; https://openscholarship.wustl.edu/cgi/viewcontent.cgi?article=1874&context=cse_research; http://dx.doi.org/10.7936/k74b2zns; https://doi.org/10.7936%2Fk74b2zns; https://dx.doi.org/10.7936/k74b2zns; https://openscholarship.wustl.edu/cse_research/873/
Washington University in St. Louis Libraries
Provide Feedback
Have ideas for a new metric? Would you like to see something else here?Let us know