Permalink
Please sign in to comment.
Browse files
Loaded up 21M edges, all of film data + names. And ran a complex quer…
…y, with a 60ms latency!
Showing
with
95 additions
and 9 deletions.
- +10 −2 commit/log.go
- +1 −0 notes.txt
- +25 −0 posting/list.go
- +4 −1 posting/lists.go
- +5 −2 server/loader/main.go
- +21 −4 server/main.go
- +29 −0 server/notes.txt
12
commit/log.go
1
notes.txt
@@ -0,0 +1 @@ | ||
+Have to increase the file limit set in Ubuntu to avoid the "too many open files" issue, probably caused by goroutines opening up RocksDB SST files. |
25
posting/list.go
5
posting/lists.go
7
server/loader/main.go
25
server/main.go
29
server/notes.txt
@@ -0,0 +1,29 @@ | ||
+curl localhost:8080/query -XPOST -d '{ | ||
+me(_xid_: m.06pj8) { | ||
+ type.object.name.en | ||
+ film.director.film { | ||
+ type.object.name.en | ||
+ film.film.starring { | ||
+ film.performance.actor { | ||
+ film.director.film { | ||
+ type.object.name.en | ||
+ } | ||
+ type.object.name.en | ||
+ } | ||
+ } | ||
+ film.film.initial_release_date | ||
+ film.film.country | ||
+ film.film.genre { | ||
+ type.object.name.en | ||
+ } | ||
+ } | ||
+} | ||
+}' > output.json | ||
+ | ||
+INFO[0554] Query Latencies json=35.434904ms package=server parsing=93.385µs process=24.785928ms total=60.314523ms | ||
+ | ||
+The first time this query runs, it's a bit slower, taking around 250ms in processing, mostly because we have to load | ||
+the posting lists from rocksdb, and use disk seeks. But, on consecutive runs, when the PLs are already in memory, | ||
+this takes under 25ms for processing. IT actually takes more time to convert the results to JSON! | ||
+ | ||
+My reactions are mixed. I'm happy, but unsatisfied. |
0 comments on commit
ca36982