News for hackers. Stuff that matters.

shironinja

Re:Extracting RAW pictures from memory dumps on Friday February 27, 2015 @01:00PM (#9120243)
Just wanted to say I loved your off the cuff humor and thought it was an enjoyable article.
Re:Highlight.js – Syntax highlighting for the Web on Friday February 20, 2015 @05:01PM (#9083354)
... that the presenter should buy a laser pointer!
Re:Major Changes from Solr 4 to Solr 5 on Thursday February 19, 2015 @02:29PM (#9076342)
It is similar in SOLR (and other NoSQL data stores) currently .. at least as far as I am aware. It can be quite intensive especially since ES, SOLR, etc like to use as much memory as they can for fast access. Any non-trivial application should have duplicate servers / instances to soak up the traffic while a change like that is migrated.
Re:Major Changes from Solr 4 to Solr 5 on Thursday February 19, 2015 @01:12PM (#9075711)
For your use case set up both and then do some testing.

Speaking for myself I did that and found that SOLR was a lot more performant. I needed a high-traffic solution without a bunch of servers.

I find that ES tries to do too much with all the dashboards and monitoring etc.

SOLR keeps it simple and thereby does not incur the performance penalty.

Also when an ES cluster goes south (cluster health "yellow" or "red") it seemed like a pain to troubleshoot and determine the real reason WHY. SOLR seems more durable and when something needs investigation you get a clear message in the log.

If you are starting something new and just don't know your traffic requirements and are scared of it "going viral" like a hot new mobile game ES may work for you though. The one thing it excels at is adding more ES servers to the cluster quickly. So if you need more servers ASAP and don't care about the cost ES has that covered.