Live data from Hacker News

GUN 0.7.9 – 15M read/sec, 15K write/sec, 2K sync/sec MIT Licensed Graph Database

github.com

11–20 of 51 posts

Re: GUN 0.7.9 – 15M read/sec, 15K write/sec, 2K sync/sec MIT Licensed Graph Database

#11

   We're getting even better numbers on other devices:

   Android phone, ~5M ops/sec.
   Macbook Air, Chrome, ~30M ops/sec.
   Macbook Pro, Chrome Canary, ~80M ops/sec.
   Lenovo netbook, IE6, ~100K ops/sec

   [...]

   These numbers represent a breakthrough in performance not possible with other databases. 

Care to share some details on this benchmark? What kind of operations were these? Your results don't really sound likely for any kind of non-trivial operation - is it possible that you were testing a routine that was optimized out (to a static return/noop) by the JIT?

from https://github.com/amark/gun/wiki/100000-ops-sec-in-IE6-on-2...

Re: GUN 0.7.9 – 15M read/sec, 15K write/sec, 2K sync/sec MIT Licensed Graph Database

#12
Do you plan to add presence to GUN? One of the key features that we require from Firebase is the ability to tell the server to delete a key in the event the client disconnects.

https://firebase.google.com/docs/reference/android/com/googl...

Re: GUN 0.7.9 – 15M read/sec, 15K write/sec, 2K sync/sec MIT Licensed Graph Database

#13

We're getting even better numbers on other devices: Android phone, ~5M ops/sec. Macbook Air, Chrome, ~30M ops/sec. Macbook Pro, Chrome Canary, ~80M ops/sec. Lenovo netbook, IE6, ~100K ops/sec [...] These numbers represent a breakthrough in performance not possible with other databases. Care to share some details on this benchmark? What kind of operations were these? Your results don't really sound likely for any kind…

yeah 5 million "ops"/second on an Android phone? I want to know what the "ops" were. Is it just reading a value from a static memory address? Network request? What's going on here?

Re: GUN 0.7.9 – 15M read/sec, 15K write/sec, 2K sync/sec MIT Licensed Graph Database

#14

We're getting even better numbers on other devices: Android phone, ~5M ops/sec. Macbook Air, Chrome, ~30M ops/sec. Macbook Pro, Chrome Canary, ~80M ops/sec. Lenovo netbook, IE6, ~100K ops/sec [...] These numbers represent a breakthrough in performance not possible with other databases. Care to share some details on this benchmark? What kind of operations were these? Your results don't really sound likely for any kind…

JS performance is terrible, it took us a year to rewrite everything from scratch to get these type of numbers.

As mentioned near the bottom of that link, they are on cached reads which is unrealistic in real world settings but a useful baseline number to compare against.

To understand our methodology on the benchmark approach, check out this tech talk on all the problems we encountered while testing (including things like you mentioned, dealing with how the JIT optimizes, or often times in Chrome, doesn't): https://youtu.be/BEqH-oZ4UXI

However, a perk of the push-based model (realtime data sync like with Firebase), is that cached reads become a lot more realistic because often the data will already be there before you read it (unlike with a pull/poll based model).

Any details I can expand on for you?

Re: GUN 0.7.9 – 15M read/sec, 15K write/sec, 2K sync/sec MIT Licensed Graph Database

#15
post #12

Do you plan to add presence to GUN? One of the key features that we require from Firebase is the ability to tell the server to delete a key in the event the client disconnects. https://firebase.google.com/docs/reference/android/com/googl...

Not yet! Good suggestion though. Deletes right now are currently very difficult in gun. But we plan on fixing that in v0.8.x releases. Your idea of being able to do it on disconnects is a great one, I'll add it to the to-do list!

Re: GUN 0.7.9 – 15M read/sec, 15K write/sec, 2K sync/sec MIT Licensed Graph Database

#17

We're getting even better numbers on other devices: Android phone, ~5M ops/sec. Macbook Air, Chrome, ~30M ops/sec. Macbook Pro, Chrome Canary, ~80M ops/sec. Lenovo netbook, IE6, ~100K ops/sec [...] These numbers represent a breakthrough in performance not possible with other databases. Care to share some details on this benchmark? What kind of operations were these? Your results don't really sound likely for any kind…

JS performance is terrible, it took us a year to rewrite everything from scratch to get these type of numbers. As mentioned near the bottom of that link, they are on cached reads which is unrealistic in real world settings but a useful baseline number to compare against. To understand our methodology on the benchmark approach, check out this tech talk on all the problems we encountered while testing (including things…

> Android phone, ~5M ops/sec.

what are the "ops" in this case?

Re: GUN 0.7.9 – 15M read/sec, 15K write/sec, 2K sync/sec MIT Licensed Graph Database

#19

Come on man, do we have to do this everytime ? Next time post on a weekday so you'll get maximum criticism. They should've implemented scylladb on top gundb, not amateur-designed-by-kernel-hackers seastar-framework. Do reavaluate your time, seriously & sincerly.

[deleted]

Re: GUN 0.7.9 – 15M read/sec, 15K write/sec, 2K sync/sec MIT Licensed Graph Database

#20

This looks really cool. I'm no database expert, but a decentralised graph database is an intriguing idea. Has it been tried before? (decentralised databases I mean, not graph databases)

I'm building one, slightly different use case though.
Post reply on HN