Thanks everyone for the responses. My motivation for TCP is coming from a very heavy indexing pipeline where the smallest of optimization matters. I am working on a machine data parser which feeds data into Cassandra and Solr and we have SLAs based on how fast we can make data available in both the sources. We used to have issues with Cassandra as well but we optimized the s**t out of it.
Now we want to do the same with Solr. While I do realize that this is going to be a lot of work, but if its something that will reap benefit in long run, then so be it. Datastax provides a netty based layer in their enterprise version which folks have reported to be faster. Now just because a commercial vendor ships it, doesn't mean we will jump into it without thinking. We will definitely do a effect-vs-effort analysis before committing to this. For majority of users, such high performance might not be a requirement/priority, so I understand the reluctance to go down this path. I think it would be best at this time that I start exploring this option and get back with my analysis. Thanks again. Saumitra -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-TCP-layer-tp4191715p4192176.html Sent from the Solr - User mailing list archive at Nabble.com.
