If you are looking for an easy to run/manage, typo tolerant search engine, I've been working on this: https://github.com/typesense/typesense
Xapiand: A fast, simple, modern search and storage engine
51–60 of 68 posts
Re: Xapiand: A fast, simple, modern search and storage engine
#52I am always surprised when I find out that developers with bold claims to fame have not heard of Sphinx [0] and of Xapian [1]! [0]: http://sphinxsearch.com/ [1]: https://xapian.org/
Those developers roll their own search libraries.
Re: Xapiand: A fast, simple, modern search and storage engine
#53From the features list:
> Ranked search (so the most relevant documents are more likely to come near the top of the results list) with built-in support for multiple models from the Probabilistic, Divergence from Randomness, and Language Modelling families of weighting models. Custom user-supplied weighting models are also supported.
Could someone explain in a little more detail what these terms mean?
Re: Xapiand: A fast, simple, modern search and storage engine
#54Xapiand depends on xapian-core which is licensed under GPL (not LGPL). Makes me think that Xapiand should be licensed under GPL, instead of MIT?
Re: Xapiand: A fast, simple, modern search and storage engine
#55I am always surprised when I find out that developers with bold claims to fame have not heard of Sphinx [0] and of Xapian [1]! [0]: http://sphinxsearch.com/ [1]: https://xapian.org/
Sphinx is a workhorse. Very light memory and CPU usage compared to the popular Elasticsearch.
Re: Xapiand: A fast, simple, modern search and storage engine
#56Xapian has a long history starting in the early 80s: https://xapian.org/history I've used Xapian extensively, but not this new Xapiand tool, so I can only speak to the actual library. Xapian is a C++ library that accesses index data files directly on disk. There are bindings for various languages, say Python, let's you do 'import xapian' and get FFI bindings to the library, then you basically open your on disk index…
I love Xapian, the quality of its recall is excellent and indexing performance very hard to find fault with. There's just a tiny problem - it's stuck with the GPL, despite a long effort to relicence the code going back years.
[deleted]
Re: Xapiand: A fast, simple, modern search and storage engine
#57Earlier quoted context omitted.
There are a lot of differences between Golang and Java. As much as I dislike writing Java when I have a choice, the JVM (with Java or whatever else on top) is a very capble tool... Could you explain what you mean by there being "no pros"? Are you maybe trying to get at the difficulty of tuning the JVM?
rust/c++/c has no gc and better performance/efficiency compared to java/golang. so you get excited for a library/db in those languages golang is kinda a java alternative. a db/search-engine in java/golang kinda sucks (it will under pressure)
While I definitely agree with you on the broad strokes of the differences between rust/c++/c and java/golang (representing languages without runtimes and those with them respectively), I'd say that golang is a bit more than a java alternative if we consider more than whether a runtime is included or not.
Of course, if the only consideration is whether a runtime is there or not, golang is identical to java but also identical to common lisp or maybe even interpreted languages like python.
I do want to point out that it's possible to write horribly buggy code in c++/c (less so in rust :), which can tank performance/efficiency when compared to a java/golang program. All things considered though, the ceiling on performance and efficiency is of course higher in manual memory management land.
Thanks for clarifying what you meant!
Re: Xapiand: A fast, simple, modern search and storage engine
#58Earlier quoted context omitted.
why do you think they called their product "elastic"? java heap size? 32gb? above that and you are in for problems
which problem? There is no problem, especially since the latest gc. Only tradeof
this is a limitation. For instance if you have billions of docs you need 200 tiny servers and have to deal with the communication/administration/monitoring between all of those. anything around 32gb and you will have perf drops everytime the GC works too hard..
Re: Xapiand: A fast, simple, modern search and storage engine
#59From the features list: > Ranked search (so the most relevant documents are more likely to come near the top of the results list) with built-in support for multiple models from the Probabilistic, Divergence from Randomness, and Language Modelling families of weighting models. Custom user-supplied weighting models are also supported. Could someone explain in a little more detail what these terms mean?
tl;dr is that those are different approaches to weighting documents in order to return the most relevant ones for a query.
For an intro to the problem space, see https://opensourceconnections.com/blog/2014/06/10/what-is-se...
If you want a lot more detail, check out the book Relevant Search.
Re: Xapiand: A fast, simple, modern search and storage engine
#60Haven't heard of Vespa? https://vespa.ai
Nobody has. There's no visibility or community around it which is a constant problem with Yahoo's open source projects. The only thing that really took off was Hadoop but there was very little back then.
Vespa is also far more heavy and complex than any other search systems mentioned here.