You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2014/06/12 16:23:02 UTC

[jira] [Commented] (LUCENE-5757) Move RAMUsageEstimator "reflector" to test-framework

    [ https://issues.apache.org/jira/browse/LUCENE-5757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029191#comment-14029191 ] 

Robert Muir commented on LUCENE-5757:
-------------------------------------

I think this method should be test-framework/o.a.l.util/RamUsageCalculator.java

So tests can compare their estimates against it, and we can remove the forbidden apis ban (there would be no more super-sneaky method overloading where one of the signatures is slow and the rest is fast).

> Move RAMUsageEstimator "reflector" to test-framework
> ----------------------------------------------------
>
>                 Key: LUCENE-5757
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5757
>             Project: Lucene - Core
>          Issue Type: Bug
>            Reporter: Robert Muir
>
> This method is "banned" already because it can crawl slowly across large object graphs. 
> I think it should be in the test framework. It needs enhancements for testing such as some way to filter what is crawled.
> Currently lots of code in lucene tries to provide accounting information but its all totally untested. We need to fix the test situation or remove Accountable and such methods completely.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org