Open miteshvp opened 7 years ago
amcp
commented
7 years ago What could be happening is that your graph has too large a degree (too many average properties/edges per vertex) for the SINGLE item data model. SINGLE item data model is meant for graphs with low degree. See the tests testEdgesExceedCacheSize and testVertexCentricQuery in SingleDynamoDBGraphTest.java for examples of this limitation in play.
miteshvp
commented
7 years ago If it helps, I have two nodes as below and one outgoing edge between them. So I highly doubt I have a large degree per vertex.
Item Node
{
"requestId": "c01a736a-7605-4656-b27e-f7839ae60927",
"status": {
"message": "",
"code": 200,
"attributes": {}
},
"result": {
"data": [{
"ilast_year_closed": [18],
"plast_year_closed": [14],
"ilast_month_opened": [17],
"last_updated": ["never"],
"ecosystem": ["test"],
"plast_month_closed": [15],
"vertex_label": ["Item"],
"plast_year_opened": [12],
"ilast_year_opened": [16],
"ilast_month_closed": [19],
"latest": ["x.x.y"],
"name": ["cdcb0378-a7de-4b2e-a079-fe48929164fb2351"],
"stars": [21],
"relative_used": ["not used"],
"spn": [20],
"deps_count": [-1],
"plast_month_opened": [13]
}],
"meta": {}
}
}
Desc Node
{
"requestId": "aabab6c9-391e-4a62-9043-01d7d69c544f",
"status": {
"message": "",
"code": 200,
"attributes": {}
},
"result": {
"data": [{
"last_updated": ["never"],
"shipped": [false],
"pname": ["e23f7f9c-4940-4ffe-8e2b-fa5370a0041c362"],
"vertex_label": ["Desc"],
"description": ["No Description"],
"cveds": ["2014-15:10"],
"version": ["x.x.x"],
"deps_count": [-1],
"licenses": ["NOLIC"],
"complexity": [1],
"pecosystem": ["test"],
"locs": [100],
"file": [1024]
}],
"meta": {}
}
}
Hi, We are facing lots of storage exceptions when system is under load. Our gremlin query checks if a vertex exists to update the property or create a new one with property. We are trying some performance benchmark for SINGLE vs MULTI data-model. During test runs for MULTI data-model, it went fine without any issues. Using SINGLE data-model we see improvements in overall response times but at the same time lots of storage related exceptions (parallelMutate). Is there any solution or work-around?