Hi, Lloyd,
Both runs are cold/warm? Memory/cache hit/miss could be a big factor if
your application is IO intensive. You need to monitor your system to
understand what is your bottleneck.
Good lucks,
Xiao Li
-dev +user
1). Is that the reason why it's always slow in the first run? Or are there
> any other reasons? Apparently it loads data to memory every time so it
> shouldn't be something to do with disk read should it?
>
You are probably seeing the effect of the JVMs JIT. The first run is
executing
