Thanks Marvin for your reply and taking a quick look on this. I will try your
second option of caching and using bitcollector. Meanwhile could you please
help me on below one,
for
>>those other fields so that they are no longer `stored`.  That will reduce
the
>>the cost of deserializaing a document.

I am running query on title only, and i require almost 4 fields only to
serve my purpose, title, content, url, urlpath. so, is there a way we can
fetch only these fields and it reduces the deserializaing cost or you mean
to say not to store the fields if those are not necessary. Please let me
know how to do it, thanks!!

-----
Regards
Rohit Singh
--
View this message in context: http://lucene.472066.n3.nabble.com/iterating-through-hits-is-there-a-way-to-improve-performance-or-can-we-run-these-iterations-in-parall-tp4329286p4329963.html
Sent from the lucy-user mailing list archive at Nabble.com.
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB