4 ms·
We're getting good results from http://traildb.io/ http://traildb.io/ and we don't have to grant Facebook a worldwide, royalty-free license to our patent pool i
by erichocean 10y ago
We're getting good results from http://traildb.io/ http://traildb.io/ and we don't have to grant Facebook a worldwide, royalty-free license to our patent pool in order to use it.
- perlgeek 10y agohttps://github.com/facebookincubator/beringei/blob/master/LICENSE https://github.com/facebookincubator/beringei/blob/master/LI... doesn't even mention patents. https://github.com/facebookincubator/beringei#license https://github.com/facebookincubator/beringei#license says "We also provide an additional patent grant." None of this sounds to me like you have to grant Facebook any patents to use Beringei.
- ivank 10y agohttps://github.com/facebookincubator/beringei/blob/master/PATENTS#L14-L26 https://github.com/facebookincubator/beringei/blob/master/PA...
- deleted 10y ago[deleted]
- buremba 10y agoI don't think TrailDB is comparable to Beringei. TrailDB is built for behavioral analytics queries while Beringei is developed for time-series aggregated metrics.
- erichocean 10y ago> time-series aggregated metrics That's exactly what we're using TrailDB for. Works great.
- no0b20 10y agoI'm curious about what kind of write speeds you are using traildb for?
- erichocean 10y agoWe trace every server request with it, across all stages of the request—approx. 10-12 events/timestamps per request—across multiple processes (think Zipkin). The per-request event streams are independent "trails" per process, and then we merge them together later and compute aggregated metrics using hdr_histogram. Individual events are typically hundreds to thousands of nanoseconds long, with about 20 nanoseconds of overhead to grab a timestamp using the rdtscp instruction. Hope that helps!
- no0b20 10y agoI'm not sure I follow everything what you wrote. I'm interested in how many inserts are you doing per second to the DB. Is it in 1000s/sec or millions/sec.
- erichocean 10y agoMillions, not thousands, of inserts per second. TrailDB is hella fast (that's why we use it).
- deleted 10y ago[deleted]
- no0b20 10y agoThanks. I will check it out.
- buremba 10y agoSo you have a batching mechanism for creating TrailDB files, right? Then you're able to query historical metrics by processing these TrailDB files.
- erichocean 10y agoCorrect. We mostly use hdr_histogram right now for the post-processing, since stable latency is what we care about. We also do some hdr_histogram processing for our dashboard in parallel to storing traces in TrailDB, and then we retain the individual traces to do longer term processing or when we're tracking down issues in production.
- buremba 10y agoDoes TrailDB pre-aggregate metrics? AFAIK it stores the raw data bucketed with an actor id (usually a server or visitor) and performs compression and some columnar storage optimizations for events of actors.
- vtuulos 10y agoGreat to hear that! We would love to hear how you are using TrailDB and what could be improved for your use case. Feel free to open issues in GitHub or drop by at our Gitter channel, https://gitter.im/traildb/traildb https://gitter.im/traildb/traildb