Search, Big Data, Analytics, Natural Language Processing
February 25, 2013 Leave a comment
We know that as of February 2013, of those Solr users who follow Sematext Blog about 75% use one some version of Solr 4.x. But today we are trying to get to another interesting stat:
What portion of Solr 4.x users use SolrCloud?
Let’s find out! Please tweet this to help us get more votes and better stats.
Please vote only if you are using Solr 4.x. Please do NOT vote if you are using 1.x or 3.x version of Solr.
February 15, 2013 2 Comments
With Solr 4.1 recently released, let’s see which version(s) of Solr people are using. Please tweet it to help us get more votes and better stats.
May 30, 2012 12 Comments
The results of this poll will be included in the ”Large Scale ElasticSearch, Solr & HBase Performance Monitoring” presentation at Berlin Buzzwords next week. Please vote and share this post to help us make this poll statistically significant!
May 30, 2012 15 Comments
The results of this poll will be included in the ”Large Scale ElasticSearch, Solr & HBase Performance Monitoring” presentation at Berlin Buzzwords next week. Please vote and share this post to help us make this poll statistically significant!
February 13, 2012 10 Comments
As you may know, Sematext runs a service we internally call SPM – Scalable Performance Monitoring, a currently-still-free SaaS for monitoring performance of Solr, HBase, and soon a few other technologies we often help our clients with. One of the things we monitor for Solr and other search technologies is the size of the index. We monitor it by periodically checking its size, number of documents in it, number of deleted documents, number of index segments, files, etc.
Recently, we had an internal discussion about how to best report the index size when the index changes over time and decided we’d ask people who run Solr (or ElasticSearch or Sensei or…) – you – what you would like to see in this report.
For example, imagine that in some 5-minute time period (say 10:00 AM to 10:05 AM) we check the index 5 times (in reality we do it much for frequently) and each time we do that we find the index has a different number of documents in it: 10, 15, 20, 25, and finally 30 documents. Now imagine this data as a graph showing the number of indexed document over time, but with the smallest time period shown being a 5 minutes interval.
At this point the question we have for you is: How many documents should this graph report for our example 10:00 – 10:05 AM period above? Should it show the minimum – 10? Average – 20? Mean – 20? Maximum -30? Something else? Minimum, average, and maximum – 10, 20, 30?
Any feedback and suggestions you give us regarding this will be greatly appreciated – thanks!
February 7, 2012 6 Comments
We use ElasticSearch more and more here at Sematext (we have a number of ElasticSearch projects right at this moment, some of them quite massive in terms of data and/or query volume). In our work we typically have only 1 ElasticSearch instance/only 1 JVM running ElasticSearch on each server in the cluster.
How about you? Do you run multiple ElasticSearch instances/JVMs per box in production?
Thank you for your feedback!
October 25, 2011 Leave a comment
Here is a quick one. What’s your Search Analytics tool of choice, if you have one?
And if you are happy or unhappy with the solution you are using, we’d love to hear what it is about your solution that is making you happy or unhappy - please leave a comment.
Thanks!
April 19, 2010 9 Comments
Lucene and Solr projects merged recently, as we mentioned in Solr Digest and Lucene Digest for March 2010. Today, their -dev mailing lists finally finally merged. Since Sematext runs the search-lucene.com service that makes these lists (and more) searchable, we need to decided how to handle this relatively drastic change.
Short version: Please tell us how you would like us to handle lucene-dev merge on search-lucene.com by selecting your choice in our Handling lucene-dev merge Poll. The 2 choices are described below.
We’ve identified 2 options, and we need your input to help us decide what the right option is:
If there is a 3rd or 4th option that we missed, please let us know via comments!
Please tell us which option you would prefer as search-lucene.com user by selecting your choice in our Handling lucene-dev merge Poll. Thank you.
