[jira] Updated: (LUCENE-388) [PATCH] IndexWriter.maybeMergeSegments() takes lots of CPU resources

[ http://issues.apache.org/jira/browse/LUCENE-388?page=all ] Yonik Seeley updated LUCENE-388: Attachment: yonik_indexwriter.diff Got it! Attatching new version with a minor change... I forgot to take into account deleted documents. After a merge, inst

[jira] Commented: (LUCENE-565) Supporting deleteDocuments in IndexWriter (Code and Performance Results Provided)

[ http://issues.apache.org/jira/browse/LUCENE-565?page=comments#action_12428035 ] Doron Cohen commented on LUCENE-565: I tried out this patch (July18), and have a few comments... First, it is nice to be able to add/remove documents with no n

[jira] Commented: (LUCENE-388) [PATCH] IndexWriter.maybeMergeSegments() takes lots of CPU resources

[ http://issues.apache.org/jira/browse/LUCENE-388?page=comments#action_12428033 ] Yonik Seeley commented on LUCENE-388: - Something is wrong with my patch... the behavior still differs from the original. I wrote a testInvariants() method, and

Prevayle-based StorageController for GDataServer

Does this exists? If don't, no problem, I can build one myself.

[jira] Commented: (LUCENE-388) [PATCH] IndexWriter.maybeMergeSegments() takes lots of CPU resources

[ http://issues.apache.org/jira/browse/LUCENE-388?page=comments#action_12427984 ] DM Smith commented on LUCENE-388: - In Eclipse you can set the run to use its own JVM. Otherwise it runs in Eclipse's JVM and it has negative memory side effects.

[jira] Commented: (LUCENE-388) [PATCH] IndexWriter.maybeMergeSegments() takes lots of CPU resources

[ http://issues.apache.org/jira/browse/LUCENE-388?page=comments#action_12427981 ] Daniel Naber commented on LUCENE-388: - I just see that this OOM is not exactly reproducible. I would have expected that it always happens when it has happened

[jira] Commented: (LUCENE-388) [PATCH] IndexWriter.maybeMergeSegments() takes lots of CPU resources

[ http://issues.apache.org/jira/browse/LUCENE-388?page=comments#action_12427976 ] Yonik Seeley commented on LUCENE-388: - Well, the patch changes what the hotspot is, so the hotspot compiler could be trying to compile different code... Danie

[jira] Commented: (LUCENE-388) [PATCH] IndexWriter.maybeMergeSegments() takes lots of CPU resources

[ http://issues.apache.org/jira/browse/LUCENE-388?page=comments#action_12427975 ] Paul Smith commented on LUCENE-388: --- This is where some tracing logging code would be useful. Maybe a YourKit memory snapshot to see what's going on.. ? I can'

[jira] Commented: (LUCENE-388) [PATCH] IndexWriter.maybeMergeSegments() takes lots of CPU resources

[ http://issues.apache.org/jira/browse/LUCENE-388?page=comments#action_12427969 ] Yonik Seeley commented on LUCENE-388: - > the problem is the same as before: I get an OutOfMemoryError using settings > that without the patch That's worrisome

[jira] Commented: (LUCENE-388) [PATCH] IndexWriter.maybeMergeSegments() takes lots of CPU resources

[ http://issues.apache.org/jira/browse/LUCENE-388?page=comments#action_12427967 ] Daniel Naber commented on LUCENE-388: - Hi Yonik, I just tested the patch: sorry, but the problem is the same as before: I get an OutOfMemoryError using setting

Re: [jira] Commented: (LUCENE-648) Allow changing of ZIP compression level for compressed fields

If you make the compression external this is already done. In order to do what the poster requires, you still need to read and update fields without reading the entire document. You just do this at a binary field level, and do all of he compression/decompression externally. I think putting the

[jira] Created: (LUCENE-652) Compressed fields should be "externalized" (from Fields into Document)

Compressed fields should be "externalized" (from Fields into Document) -- Key: LUCENE-652 URL: http://issues.apache.org/jira/browse/LUCENE-652 Project: Lucene - Java Issue T

[jira] Updated: (LUCENE-642) GData Server IndexComponent

[ http://issues.apache.org/jira/browse/LUCENE-642?page=all ] Simon Willnauer updated LUCENE-642: --- Attachment: bulid_xml.diff The test failed due to a class could not be build depending on a third party jar. Yonik, could you run the tests after apply

[jira] Updated: (LUCENE-388) [PATCH] IndexWriter.maybeMergeSegments() takes lots of CPU resources

[ http://issues.apache.org/jira/browse/LUCENE-388?page=all ] Yonik Seeley updated LUCENE-388: Attachment: yonik_indexwriter.diff How does this patch look? It's designed to exactly match the previous merging behavior, and it's conservative (an exact cou

[jira] Commented: (LUCENE-635) [PATCH] Decouple locking implementation from Directory implementation

[ http://issues.apache.org/jira/browse/LUCENE-635?page=comments#action_12427913 ] Michael McCandless commented on LUCENE-635: --- Awesome, thanks Otis! Have a great vacation! > [PATCH] Decouple locking implementation from Directory imple

[jira] Commented: (LUCENE-635) [PATCH] Decouple locking implementation from Directory implementation

[ http://issues.apache.org/jira/browse/LUCENE-635?page=comments#action_12427906 ] Otis Gospodnetic commented on LUCENE-635: - I took a look at it a few weeks back. If nobody takes care of it, I'll look at it again and hopefully commit it

[jira] Assigned: (LUCENE-388) [PATCH] IndexWriter.maybeMergeSegments() takes lots of CPU resources

[ http://issues.apache.org/jira/browse/LUCENE-388?page=all ] Yonik Seeley reassigned LUCENE-388: --- Assignee: Yonik Seeley > [PATCH] IndexWriter.maybeMergeSegments() takes lots of CPU resources > --

[jira] Commented: (LUCENE-635) [PATCH] Decouple locking implementation from Directory implementation

[ http://issues.apache.org/jira/browse/LUCENE-635?page=comments#action_12427857 ] Michael McCandless commented on LUCENE-635: --- Has anyone had a chance to look at this patch? This should be fully backwards compatible: old APIs have not

Re: [jira] Resolved: (LUCENE-478) CJK char list

Hi Steven, I understood (and still do, actually) 5.b as "added U+3d2e - U+4DB5 and excluded", so I expected to see the U+3d2e - U+4DB5 range in the patch, but I didn't see it. The closest range was this: + "\u3400"-"\u4db5", I'm about to go on vacation (no TV, no radio, no email, no

[jira] Commented: (LUCENE-388) [PATCH] IndexWriter.maybeMergeSegments() takes lots of CPU resources

[ http://issues.apache.org/jira/browse/LUCENE-388?page=comments#action_12427821 ] Otis Gospodnetic commented on LUCENE-388: - Ah, too bad. :( Reverted. I do recall seeing maybeMergeSegments being called a lot, although I don't recall ho