{"title":"相对论规划的一个例子","authors":"Philip W. Howard, J. Walpole","doi":"10.1145/2414729.2414735","DOIUrl":null,"url":null,"abstract":"Programmers traditionally assume we live and program in a sequentially consistent world. Hardware developers have long since abandoned sequential consistency in order to develop higher performance computers. In this paper, we argue that the natural world maintains causal consistency not sequential consistency. From that observation, we argue that concurrent programs only need to maintain causal consistency. Since causal consistency does not require a total order on operations, it can be implemented with less impact on scalability than more strict ordering guarantees.","PeriodicalId":137547,"journal":{"name":"RACES '12","volume":"38 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2012-10-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"2","resultStr":"{\"title\":\"A case for relativistic programming\",\"authors\":\"Philip W. Howard, J. Walpole\",\"doi\":\"10.1145/2414729.2414735\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Programmers traditionally assume we live and program in a sequentially consistent world. Hardware developers have long since abandoned sequential consistency in order to develop higher performance computers. In this paper, we argue that the natural world maintains causal consistency not sequential consistency. From that observation, we argue that concurrent programs only need to maintain causal consistency. Since causal consistency does not require a total order on operations, it can be implemented with less impact on scalability than more strict ordering guarantees.\",\"PeriodicalId\":137547,\"journal\":{\"name\":\"RACES '12\",\"volume\":\"38 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2012-10-21\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"2\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"RACES '12\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1145/2414729.2414735\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"RACES '12","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1145/2414729.2414735","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Programmers traditionally assume we live and program in a sequentially consistent world. Hardware developers have long since abandoned sequential consistency in order to develop higher performance computers. In this paper, we argue that the natural world maintains causal consistency not sequential consistency. From that observation, we argue that concurrent programs only need to maintain causal consistency. Since causal consistency does not require a total order on operations, it can be implemented with less impact on scalability than more strict ordering guarantees.