7595:
-
Commit 40a8b4edb4cfc7de5b62037fdcb389afa247573d in lucene-solr's branch
refs/heads/branch_6x from [~thetaphi]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=40a8b4e ]
LUCENE-7595: Disable another test not compatible with RamUsageTester
> RAMUsageTester in test-framewor
7595:
-
Commit d65c02e8cc14f03389c2426ea3d3ddd75e12b1ec in lucene-solr's branch
refs/heads/master from [~thetaphi]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=d65c02e ]
LUCENE-7595: Disable another test not compatible with RamUsageTester
> RAMUsageTester in test-framework and
7595:
-
Commit 80512ec412c20517341ddd50c78baf5270fcdc2f in lucene-solr's branch
refs/heads/branch_6x from [~thetaphi]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=80512ec ]
LUCENE-7595: Fix bug with RamUsageTester incorrectly handling Iterables outside
Java Runtime
> RAMUsageTe
7595:
-
Commit db9190db9372ae88a7392a7186397441ce070a96 in lucene-solr's branch
refs/heads/master from [~thetaphi]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=db9190d ]
LUCENE-7595: Fix bug with RamUsageTester incorrectly handling Iterables outside
Java Runtime
> RAMUsageTe
)
6.x
> RAMUsageTester in test-framework and static field checker no longer works
> with Java 9
> -
>
> Key: LUCENE-7595
> URL: https://issues.apache.org/jira/
7595:
-
Commit ea7db0a176979559e874b292522fa7006b578882 in lucene-solr's branch
refs/heads/branch_6x from [~thetaphi]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=ea7db0a ]
LUCENE-7595: Improve RAMUsageTester in test-framework to estimate memory usage
of runtime classes and work wi
7595:
-
Commit f29d2b5668296dfcdb8d650305449674faa29847 in lucene-solr's branch
refs/heads/master from [~thetaphi]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=f29d2b5 ]
LUCENE-7595: Improve RAMUsageTester in test-framework to estimate memory usage
of runtime classes and work with
54307). But I think it's ok --
better to overestimate here and blow up early and there's no way to check which
representation (byte or char-based) was actually chosen by the jvm. Yes, we
could reimplement the Latin1 vs. UTF16 heuristic, but it seems like an
overkill. :)
> RAMUsageT
9 AM:
-
Here is my patch that makes test works on whole Lucene:
- On Java 9 it disables the static leak detector
- RamUsageTester was fixed to have some "shortcuts" which are used if Java 9+
is detected: String/StringBuffer/StringBuilder and some other types are
calculated usin
Java 9 it disables the static leak detector
- RamUsageTester was fixed to have some "shortcuts" which are used if Java 9+
is detected: String/StringBuffer/StringBuilder and some other types are
calculated using their length/capacity. It also estimates memory usage of Maps
and Iterabl
fied reference fields.
> RAMUsageTester in test-framework and static field checker no longer works
> with Java 9
> -
>
> Key: LUCENE-7595
> URL: https://issues.apache.
at is not final (constant) and points to
an Object except: Strings and native (wrapper) types.
In addition we also have RAMUsageTester, that has similar problems and is used
to compare estimations of Lucene's calculations of
Codec/IndexWriter/IndexReader memory usage with reality. We sh
[
https://issues.apache.org/jira/browse/LUCENE-7595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-7595:
--
Labels: Java9 (was: )
> RAMUsageTester in test-framework and static field checker no lon
Uwe Schindler created LUCENE-7595:
-
Summary: RAMUsageTester in test-framework and static field checker
no longer works with Java 9
Key: LUCENE-7595
URL: https://issues.apache.org/jira/browse/LUCENE-7595
Is RamUsageTester supposed to work for cases where direct memory is
allocated (like with ByteBuffer's)?
I had a made a change to use direct ByteBuffer's in an Accountable object
and adjusted ramBytesUsed to reflect the memory used, but that seems to
upset tests using RamUsageTester
15 matches
Mail list logo
