[
https://issues.apache.org/jira/browse/LUCENE-3667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13175744#comment-13175744
]
Robert Muir commented on LUCENE-3667:
-------------------------------------
I only have 8GB, but on that machine, the tests don't even seem to put a dent
into the machine... like they are fast, I'm not even aware they are running.
On the 4GB laptop (without SSD), turning on the tests makes it sound like an
airplane and i cant even read gmail.
So I think we should tune the tests to not require a 'beast' computer, they
should run reasonably well on 'normal' computers too.
A few problems besides # of threads:
* we have a few tests that take absurd times (TestIndexWriterDelete: 120seconds
on my laptop). We should fix these bad apples so we arent relying upon multiple
threads so much anyway. I think TestSort is absurd too.
* I think ideally our tests should work without -Xmx512m, maybe we can get them
all passing with 256m and keep simpletext/memory under control better.
* We can always revisit tuning some of the more absurd params for mergefactor
and stuff so this happens with less probability...
> Consider changing how we set the number of threads to use to run tests.
> -----------------------------------------------------------------------
>
> Key: LUCENE-3667
> URL: https://issues.apache.org/jira/browse/LUCENE-3667
> Project: Lucene - Java
> Issue Type: Improvement
> Reporter: Mark Miller
> Assignee: Mark Miller
> Priority: Minor
>
> The current way we set the number of threads to use is not expressive enough
> for some systems. My quad core with hyper threading is recognized as 8 CPUs -
> since I can only override the number of threads to use per core, 8 is as low
> as I can go. 8 threads can be problematic for me - just the amount of RAM
> used sometimes can toss me into heavy paging because I only have 8 GB of RAM
> - the heavy paging can cause my whole system to come to a crawl. Without
> hacking the build, I don't think I have a lot of workarounds.
> I'd like to propose that switch from using threadsPerProcessor to
> threadCount. In some ways, it's not as nice, because it does not try to scale
> automatically per system. But that auto scaling is often not ideal (hyper
> threading, wanting to be able to do other work at the same time), so perhaps
> we just default to 1 or 2 threads and devs can override individually?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
