For future reference, I had this problem, and it was the debug statements in
commons HTTP that were printing out all the binary data to the log, but my
console appender was set to INFO so I wasn't seeing them. Setting http
commons to INFO level fixed my speed issue (two orders of magnitude faster).
sometorment later
I found the reason ofsolr replication'slow speed. It's not solr's problem.It's
jetty's. I used to embed jetty7 in my app. But when I found solr's demo use
jetty6 , I tried to use jetty6 in my app and I was so happy to get the fast
speed.
actually, I tried to change solr's d
This is the time to replicate and open the new index, right? Opening a
new index can take a lot of time. How many autowarmers and queries are
there in the caches? Opening a new index re-runs all of the queries in
all of the caches.
2010/11/1 kafka0102 :
> I suspected my app has some sleeping op ev
I hacked SnapPuller to log the cost, and the log is like thus:
[2010-11-01
17:21:19][INFO][pool-6-thread-1][SnapPuller.java(1037)]readFully1048576 cost 979
[2010-11-01
17:21:19][INFO][pool-6-thread-1][SnapPuller.java(1037)]readFully1048576 cost 4
[2010-11-01
17:21:19][INFO][pool-6-thread-1][Snap
