Good question. We already talked about it on skype.

In short: unit tests should be short.. so they should not rely on 10.000
items. If you want that much data, create a slow test(s) that deal with a
big chunk of memory. I would love if you could create a test that tried to
reflect a real world application wich gigabytes of data in combination with
near caching.. and see if it still works..

Currently our nightly tests are not yet set up in such a way.. but you
could place hundred(s) of megabytes of data in memory without a problem.
But soon I hope that our tests will do at least twice the amount of load
regular customers are doing... We are talking about a full scale cluster
here with at least a hundreg gig of data and 50/100 nodes.


On Wed, Mar 5, 2014 at 10:43 AM, Enes Akar <notifications@github.com> wrote:

> In hazelcast/src/test/java/com/hazelcast/map/EvictionTest.java:
>
> > @@ -327,8 +321,8 @@ public void run() {
> >              }.start();
> >          }
> >
> > -        assertEquals(latch.await(10, TimeUnit.MINUTES), true);
> > -        assertEquals(0, failCount.get());
> > +        assertOpenEventually(latch,5*60);
>
> Peter;
> What if a test takes several seconds in normal conditions (running as a
> single test in my local machine), but when it is run parallel, putting
> 10000 put may take minutes.
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/hazelcast/hazelcast/pull/1912/files#r10291200>
> .
>