Dear all,
I have created a new Topic: "Ignite SQL Indexing Performance problems" since
the conversation has deviate a lot form the original subject.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p12347
than 2
million entries.
So could you please provide a concrete feedback?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p12335.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
gt;> Could you please elaborate more on this topic and if/what will change at
>> version 2.0? Should I open a different topic better?
>>
>>
>>
>> --
>> View this message in context: http://apache-ignite-users.705
>> 18.x6.nabble.com/Distributed-Closures-VS-Executor-Service-t
>> p11192p12314.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>
xing will be used anyway.
>
> Could you please elaborate more on this topic and if/what will change at
> version 2.0? Should I open a different topic better?
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Distributed-Closures-VS
will change at
version 2.0? Should I open a different topic better?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p12314.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
which I described in my
previous posts of this thread.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p12263.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
IgniteKernal%ppsp-cluster-IV]
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=82a8c42c, name=ppsp-cluster-IV, uptime=00:13:06:486]
> ^-- H/N/C [hosts=1, nodes=2, CPUs=8]
> ^-- CPU [cur=52.13%, avg=10.12%, GC=7.77%]
> ^-- Heap [used=
t 'metricsLogFrequency' to 0)
^-- Node [id=b5843eb9, name=ppsp-cluster-IV, uptime=00:13:01:516]
^-- H/N/C [hosts=1, nodes=2, CPUs=8]
^-- CPU [cur=100%, avg=10.29%, GC=107.47%]
^-- Heap [used=5987MB, free=2.54%, comm=6143MB]
^-- Non heap [used=235MB, free=-1%, comm=238MB]
^-- Public thread pool [active=0, idle=0, qSize=0]
^-- System thread pool [active=0, idle=0, qSize=0]
^-- Outbound messages queue [size=0]
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p12168.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p11863.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
I have to perform though, I must have
all the products rows of each distinct category.
So in case of PARTITIONED cache, if I do broadcast, then there is no
guarantee that the categories assigned to a job will have all the rows at
the local cache.
--
View this message in context:
http://apa
(java.util.Collection)
I still think the original approach I suggested is easier and makes more
sense...
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p11817.html
Sent from the Apache Ignite Users mailing list
Hello Christo,
Thank you for your prompt response. I will check your idea and get back to
you and the community.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p11759.html
Sent from the Apache Ignite Users
to do the required calculations and
write the results etc.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p11758.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
hannels;
private int channelType;
private int weekStart;
private int weekEnd;
}
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p11742.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
e a way I make
> sure each node has all the data that will query locally? In combination with
> Compute Task Adapter always.
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p1173
this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p11739.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-
> tp11192p11653.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
SQL query on the table that will be loaded and maintained in cache but on
the rows that it keeps locally.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p11653.html
Sent from the Apache Ignite Users mailing
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p11609.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
ext available to Ignite.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p11519.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p11517.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
in context:
http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p11490.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
s
them as argument in callables or put them in the distributed cache for the
callables to pick them up from there?
Thank you.
--
View this message in context: Distributed Closures VS Executor Service
<http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS
/IgniteThreadPoolExecutor.java
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192p11478.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
/Distributed-Closures-VS-Executor-Service-tp11192p11287.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
to pick them up from there?
Thank you.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Distributed-Closures-VS-Executor-Service-tp11192.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
26 matches
Mail list logo
