Live data from Hacker News

Viewing profile — xavcochran

xavcochran

HN member
Joined
Mon, Mar 13, 2023, 9:23 AM UTC
HN karma
13
Public activity
22 items

About xavcochran

Avid Rust developer and founder of HelixDB (YC X25)

Recent public activity

  1. story
  2. comment
    Comment #49411963

    I made a byte-range cache for object storage. For full hits it's zero copy. On a miss, it fetches only the missing bytes from object storage needed to serve the request. It merges …

  3. story
  4. comment
  5. story
  6. comment
  7. story
  8. comment
  9. story
  10. comment
    Comment #43990552

    The benefit of baking in the dimension and size of individual elements (the precision) is the fact that the size will be known at compile time meaning it can be allocated on the st…

  11. comment
    Comment #43987493

    We utilize some of LMDB's optimizations such as the APPEND put flags. We also make use of LMDB handling duplicates as a one-to-many key instead of duplicating keys. This means we c…

  12. comment
    Comment #43987261

    Looking at your benchmarks you say for inserting 1k edges its around 500,000 ns/iteration. Is this 500,000 ns/per edge insertion or for all 1k of them?

  13. comment
    Comment #43984035

    thank you! any feedback would be much appreciated

  14. comment
  15. comment
    Comment #43982793

    there is also the fact that the more dimensions you have for embedded data the more diluted the embedding becomes so it is unusual to go anywhere near the limits of vector length!

  16. comment
    Comment #43982711

    very interesting, will look into this. I know for a fact that you cannot compile the likes of LMDB and RocksDB to work with WASM but this looks promising for our custom storage eng…

  17. comment
    Comment #43982353

    We will definitely look into it. The SPLADE models look promising!

  18. comment
    Comment #43982342

    to add to George's reply, for helix to run on the browser with WASM the storage engine has to be completely in memory. At the moment we use LMDB which uses file based storage so th…

  19. comment
    Comment #43982324

    thanks for the question! we chose f64 as a default for now as just to cover all cases and we believed that basic vector operations would not be our bottleneck initially. As we opti…

  20. comment
    Comment #43982297

    apart from the fact Cozo seems to be pretty dead, we use a different storage engine which makes our reads much faster. based on their benchmarks I estimate our most of our reads to…

  21. comment
    Comment #43982204

    Assuming you are using GPUs for model inference, the best way to set it up would have the DB and a separate server to send inference requests. Note that we plan on support custom m…

  22. comment
    Comment #43982060

    Thanks for the kind words! At the moment the query language transpilation is quite unstable but we are in the process of a large remodel which we aim to finish in the next day or s…