On Wed, Oct 19, 2011 at 8:24 AM, Richard Yunhua Sang
wrote:
> After more testing, I've seen the WeakReference impl. failed when JVM was
> very busy in multi-threaded operations. Although the SoftReference impl.
> survived in my test cases, it may fails too in radical situation of JVM.
>
> The Guav
After more testing, I've seen the WeakReference impl. failed when JVM was
very busy in multi-threaded operations. Although the SoftReference impl.
survived in my test cases, it may fails too in radical situation of JVM.
The Guava does support Lazy operations, but its API is not that friendly.
Tha
I'm curious what Guava (the google Java functional programming
library) does in this situation? I'm not sure they even try for
laziness.
On Tue, Oct 18, 2011 at 5:57 PM, Richard Yunhua Sang
wrote:
> Thanks for the new method, it's more easier to create a flow now.
>
> I have tried to use WeakRef
Thanks for the new method, it's more easier to create a flow now.
I have tried to use WeakReference/SoftReference to replace the rest property
in LazyFlow, both worked even in low memory scenario (-Xmx128m). The problem
is that the resolved Flow cannot be reused, it'll cause NPE since the
referenc
On Fri, Oct 14, 2011 at 1:22 PM, Richard Yunhua Sang
wrote:
> Tapestry 5 version: 5.3-beta19
>
> I love the API of tapestry-func, Today when I use tapestry-func to process a
> file with 3 million lines, I get following exception:
>
> Exception in thread "main" java.lang.OutOfMemoryError: Java heap
Tapestry 5 version: 5.3-beta19
I love the API of tapestry-func, Today when I use tapestry-func to process a
file with 3 million lines, I get following exception:
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOfRange(Arrays.java:3209)
at java.lang
