a warm-up before the code will otimizirovan" exactly
> mean?
> What shoulde I do about the warm-up?
>
> Er...
>
> Question is not that complicated.It's not about continuous query.
> Can you explain why more nodes spend more time when I execute sql query in
> partationed mode?
> Theoretically more nodes should be faster?
>
>
--
Vladislav Pyatkov
out the warm-up?
Er...
Question is not that complicated.It's not about continuous query.
Can you explain why more nodes spend more time when I execute sql query in
partationed mode?
Theoretically more nodes should be faster?
Hi,
Are you sure, you correct measure?
JVM need a warm-up before the code will otimizirovan.
What cluster topology:
Where is fisical machines (witn Ignite node) located?
Where is located client node (where you do benchmark)?
On Wed, Jun 22, 2016 at 11:38 AM, Level D <724172...@qq.com> wrote:
>
Thanks for asking.
I'm trying to get faster reads. Write is good for now.
Here's my read example. It's just testing environment.
I have two caches, Cache1 and Cache2. And preload 45,000 tips in Cache1. Put
1,000,000 tips into Cache2 to trigger continuous query in Cache1. After the
end, cons
Hello,
Need more detail: which task you try to solve, how you measure delay on
read and so on.
Obviously you can get networking overhead for data which stores on remote
node.
But compared to REPLECATED cache you do not waste time copying data to all
nodes on write.
Can you provide example?
On W
Hi,
I demand both read and write operations, so I chose partitioned mode cache.
When I increased my cluster by one node, I got slower reads.
Is there any way to make it faster?