pisa
resin
pisa | resin | |
---|---|---|
1 | 2 | |
859 | 564 | |
1.5% | - | |
8.0 | 0.0 | |
15 days ago | 5 months ago | |
C++ | C# | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pisa
-
A Compressed Indexable Bitset
The EF core algorithm implemented in folly [3] may be a bit faster, and implementing partitioning on top of that is relatively easy.
It would definitely compress much better than roaring bitmaps. In terms of performance, it depends on the access patterns. If very sparse (large jumps) PEF would likely be faster, if dense (visit a large fraction of the bitmap) it'd be slower.
It is possible to squeeze a bit more compression out of PEF by introducing a chunk type for Elias-Fano of the chunk complement (for very dense chunks), but you lose the operation of skipping to a given position, which is however not needed in inverted indexes (you only need to skip past a given id, and that can be supported efficiently). That is not mentioned in the paper because at the time I thought the skip-to-position operation was a non-negotiable.
[1] https://github.com/ot/ds2i/
[2] https://github.com/pisa-engine/pisa
[3] https://github.com/facebook/folly/blob/main/folly/experiment...
resin
-
Ask HN: May I sell the copyright to my code?
I've built a search engine. It has its own query language, data structures and binary file formats, it's MIT licensed and it has around 60 forks. Nobody uses it though, even though it has been around for some years but it was just until recently that I managed to solve the very last of the most crucial of bugs, so I don't find that surprising at all.
It works well now, though, for a Wikipedia sized text based corpus, even though it's still in beta and contains code that can still be optimized. However, before I want to go any further with the project, I'd like to see if I can sell it, the copyright to my code, that is. Because maybe I want to be in the business of creating smart code, then sell it, then move on to the next thing? And maybe some company would like to have a search engine in their software portfolio? Suppose we meet, have a drink, see what happens.
Do I have the rights to sell it, though?
I'm the author of 99.999% of the commits.
https://github.com/kreeben/resin
- Show HN: Hardware-accelerated vector-based search engine for image and text
What are some alternatives?
lucene - Apache Lucene open-source search software
Apache Solr - Apache Lucene and Solr open-source search software
kitten - A statically typed concatenative systems programming language.
efg - GPU based Compressed Graph Traversal
MeTA - A Modern C++ Data Sciences Toolkit
Studybyte - Studybyte is a search engine designed to help students find educational content effortlessly.
Typesense - Open Source alternative to Algolia + Pinecone and an Easier-to-Use alternative to ElasticSearch ⚡ 🔍 ✨ Fast, typo tolerant, in-memory fuzzy Search Engine for building delightful search experiences
RarbgAdvancedSearch - Rarbg Advanced Search is an advanced search tool for the popular torrent site Rarbg
alexandria - Full text search engine powering Alexandria.org - the open search engine.
SmartImage - Reverse image search tool (SauceNao, IQDB, Ascii2D, trace.moe, and more)