Re: Designing Affinity Key for more locality

Hi William, Can you describe the use case and domain model in more detail? 1. AffinityKey is used to colocate some data with other data. What do you achieve with user-id being the affinity key? 2. If you'd like to put all users for a given tenant/group to the same node for efficiency, the

Re: Designing Affinity Key for more locality

Came across this statement in the Data Partitioning documents: "The affinity function determines the mapping between keys and partitions. Each partition is identified by a number from a limited set (0 to 1023 by default)." Looks like there is no point for adding another layer of mapping unless I

Designing Affinity Key for more locality

Hi, I am currently using user-id as the affinity key and because it is a uuid/string, it will distribute across all partitions in the cluster. However, for my scenario, I am writing and reading users that are for the same tenant/group so it seems to me that it is better to design with more read/wr

Re: Poor Performance with Increasing Public Thread Pool Size

Hi Adrian, One thing I would be careful about in .Net IA clients is managing the numbers of allocations. Your test suggests the compute func being sent to the node contains a large number of objects (10 in the case of your test scaffold). Increasing the size of the public thread pool will inc

Re: Cannot start ignite nodes with shared memory - Ignite version 2.10.0

Thankyou Ilya. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Poor Performance with Increasing Public Thread Pool Size

Hi Igniters, We are using the .net API for Ignite to distribute computing tasks (closures) to a cluster. We are having an issue involving the public thread pool size - when the tasks are sent to a machine with the default public thread pool size (48 processors, 48 threads in the case of our te

Re: Cannot disable system view JMX exporter via configuration

Thanks for the reply. As a workaround, now I'm adding below whitelist to my prometheus.yaml and it's working. whitelistObjectNames: - "java.lang:type=OperatingSystem" - "java.lang:type=Threading" - "java.lang:type=Memory" tsippo -- Sent from: http://apache-ignite-users.70518.x6.nabble.com

Webinar >> How to Use Spark With Apache Ignite for Big Data Processing

Hi Igniters! I'm going to talk about Apache Ignite Spark integration and run live demo examples during the following webinar: https://www.gridgain.com/resources/webinars/how-use-spark-apache-ignite-big-data-processing If you'd like to learn more about the existing API, take a look at some use ca

Webinar: How to Use Spark With Apache Ignite for Big Data Processing

Hi Igniters! I'm going to talk about Apache Ignite Spark integration and run live demo examples during the following webinar: https://www.gridgain.com/resources/webinars/how-use-spark-apache-ignite-big-data-processing

rebalancing & K8

Hi folks If I am deploying my ignite cluster using AKS, is defining the auto discovery service sufficient? I am following this link: https://ignite.apache.org/docs/latest/installation/kubernetes/azure-deployment Specifically, I am concerned about ignite's node/partition rebalancing in case of au

Re: Ignite 2.10. Performance tests in Azure

The challenge is that by using large numbers of records in a single putAll method, you’re effectively creating a huge transaction. Transactions require distributed locks, which are expensive. You’re right that batching can improve throughput (but not latency). That’s what the data streamer does

Re: Ignite 2.10. Performance tests in Azure

Hi, I have the same feeling, but I think that shouldn't be the case. Small number of big batches should decrease the total latency time while would favor the total throughput. And, as Ilya said: "In a distributed system, throughput will scale with cluster growth, but latency will be steady or be