: Eks: just for grins, you can sometimes save a single cycle by changing
: "id==-1" to "id<0" (many operations on x86 automatically set status
can you save anymore if you use "0>id" ? :)
-Hoss
-
To unsubscribe, e-mail: [EMA
[
https://issues.apache.org/jira/browse/LUCENE-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617631#action_12617631
]
Yonik Seeley commented on LUCENE-1345:
--
Eks: just for grins, you can sometimes save a
Can you post a patch with your full changes to DocumentsWriter and
IndexWriter?
That first thread is trying to flush, but is waiting for all threads
to leave DocumentsWriter (finish adding docs). The 2nd thread looks
like it's waiting for the flush to finish before proceeding. Are
the
tabpanels:comment-tabpanel&focusedCommentId=12617604#action_12617604
>
> ]
>
> Paul Elschot commented on LUCENE-1345:
> --
>
> 20090729 is the date here, the attachment is dated 20080728, never mind.
>
> As to the sentinel f
[
https://issues.apache.org/jira/browse/LUCENE-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617606#action_12617606
]
Paul Elschot commented on LUCENE-1345:
--
Indeed, it makes sense to add the changes fro
t is dated 20080728, never mind.
As to the sentinel for doc()/next() in the TestIteraratorPerf patch: this will
need some real Scorers/DocIdSetIterators to see actual JIT compiler inlining in
both cases. In the patch, the Old and New classes are local private classes,
which are much easier to in
[
https://issues.apache.org/jira/browse/LUCENE-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617603#action_12617603
]
Eks Dev commented on LUCENE-1345:
-
great! Will look into at at the weekend in more datails
[
https://issues.apache.org/jira/browse/LUCENE-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Elschot updated LUCENE-1345:
-
Attachment: LUCENE-1345.patch
Patch of 20080729: all tests pass, but no tests cases for filter c
Would anyone be having any insight into deadlock issues, when running
DocumentsWriter.java from multiple threads ?. I am trying to port
ParallelWriter.java code to new codebase of DocumentsWriter.java and
IndexWriter. I am doing this by splitting, DocumentsWriter.addDocument call
into two metho
[
https://issues.apache.org/jira/browse/LUCENE-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eks Dev updated LUCENE-1345:
Attachment: TestIteratorPerf.java
Hi Paul,
I gave it a try on micro benchmarking, and it looks like we co
Would anyone be having any insight into deadlock issues, when running
DocumentsWriter.java from multiple threads ?. I am trying to port
ParallelWriter.java code to new codebase of DocumentsWriter.java and
IndexWriter. I am doing this by splitting, DocumentsWriter.addDocument call
into two metho
>>... to change semantics of these iterators not to return boolen but
> > rather document Id with sentinel values. This would definitely reduce
> > number of method invocations by factor 2 at least.--- {next() doc()}
> > -> next()
> >
> > It would be pretty easy to do that, just requires on one h
[
https://issues.apache.org/jira/browse/LUCENE-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley resolved LUCENE-1346.
--
Resolution: Fixed
Fix Version/s: 2.4
committed.
> replace Vector with ArrayList in Que
13 matches
Mail list logo
