{"title":"标记属性图:SQL或NoSQL?","authors":"Dmitry Anikin, O. Borisenko, Y. Nedumov","doi":"10.1109/IVMEM.2019.00007","DOIUrl":null,"url":null,"abstract":"There are two main approaches to graph databases: based on RDF model and based on labeled property graph model. RDF is well known and studied, but modern graph databases with labeled property graph model are studied much lesser. In this paper we evaluated several possible solutions for storing and querying graph data using Gremlin - general purpose graph query language from Apache TinkerPop. We used LDBC Graphalytics framework and compared NoSQL-based setups with SQL-based setups. We evaluated JanusGraph on HBase both on single machine and cluster and SQLG on top of PostgreSQL and H2. We used datasets from the different domains and of different sizes up to tens of millions vertices and edges. Evaluation results show that for the used workload SQLG with PostgreSQL is about ten times faster than JanusGraph on HBase and SQLG with H2 performance is in between.","PeriodicalId":166102,"journal":{"name":"2019 Ivannikov Memorial Workshop (IVMEM)","volume":"20 ","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2019-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"3","resultStr":"{\"title\":\"Labeled Property Graphs: SQL or NoSQL?\",\"authors\":\"Dmitry Anikin, O. Borisenko, Y. Nedumov\",\"doi\":\"10.1109/IVMEM.2019.00007\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"There are two main approaches to graph databases: based on RDF model and based on labeled property graph model. RDF is well known and studied, but modern graph databases with labeled property graph model are studied much lesser. In this paper we evaluated several possible solutions for storing and querying graph data using Gremlin - general purpose graph query language from Apache TinkerPop. We used LDBC Graphalytics framework and compared NoSQL-based setups with SQL-based setups. We evaluated JanusGraph on HBase both on single machine and cluster and SQLG on top of PostgreSQL and H2. We used datasets from the different domains and of different sizes up to tens of millions vertices and edges. Evaluation results show that for the used workload SQLG with PostgreSQL is about ten times faster than JanusGraph on HBase and SQLG with H2 performance is in between.\",\"PeriodicalId\":166102,\"journal\":{\"name\":\"2019 Ivannikov Memorial Workshop (IVMEM)\",\"volume\":\"20 \",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2019-09-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"3\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2019 Ivannikov Memorial Workshop (IVMEM)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/IVMEM.2019.00007\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2019 Ivannikov Memorial Workshop (IVMEM)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/IVMEM.2019.00007","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
There are two main approaches to graph databases: based on RDF model and based on labeled property graph model. RDF is well known and studied, but modern graph databases with labeled property graph model are studied much lesser. In this paper we evaluated several possible solutions for storing and querying graph data using Gremlin - general purpose graph query language from Apache TinkerPop. We used LDBC Graphalytics framework and compared NoSQL-based setups with SQL-based setups. We evaluated JanusGraph on HBase both on single machine and cluster and SQLG on top of PostgreSQL and H2. We used datasets from the different domains and of different sizes up to tens of millions vertices and edges. Evaluation results show that for the used workload SQLG with PostgreSQL is about ten times faster than JanusGraph on HBase and SQLG with H2 performance is in between.