Hi,
On 19/08/14 14:43, Thomas Mueller muel...@adobe.com wrote:
Limiting the cache size by number of entries doesn't make sense. It is a
sure way to run into out of memory, exactly because the sizes of documents
varies a lot.
I agree with Thomas. I think there must always be a way to tell the
Hi,
oak-commons might be a good fit...
regards
marcel
On 19/08/14 09:17, Davide Giannella dav...@apache.org wrote:
Hello team,
as part of OAK-2035 I had to copy some helpers from oak-core to
oak-jcr. I was in a hurry so I copied
Hi
Am 20.08.2014 um 09:43 schrieb Marcel Reutegger mreut...@adobe.com:
Hi,
oak-commons might be a good fit…
In the test artifact attachment ?
I would suggest not to add test classes to the primary artifact.
Regards
Felix
regards
marcel
On 19/08/14 09:17, Davide Giannella
Hi,
If we need a limit on the number of entries for some other (internal)
reason, like consistency check, then I understand. If we later find a way
to speed up consistency check (or if we don't need it, which I would
prefer), then this is no longer needed. But I also don't know how to limit
by
why is 256MB -- the default value -- sufficient/insufficient
We don't know. But how do you know that a cache of 10'000 entries is
sufficient? Specially if each entry can be either 1 KB or 1 MB or 20 MB.
The available memory can be divided into different areas, and each
component is given a
Hi,
On 20/08/14 10:23, Felix Meschberger fmesc...@adobe.com wrote:
Am 20.08.2014 um 09:43 schrieb Marcel Reutegger mreut...@adobe.com:
Hi,
oak-commons might be a good fitŠ
In the test artifact attachment ?
I would suggest not to add test classes to the primary artifact.
oops, you are
