Re: Test suit failures after upgrade to 2.13 (because IN no longer accepts a Java array)

org/jira/browse/IGNITE-13056> [6] https://issues.apache.org/jira/browse/IGNITE-16991 > 17 мая 2022 г., в 12:16, Courtney Robinson написал(а): > > Hey, > I just checked and it doesn't seem as if any of the test cases use arrays > with more than 1 element in them. > It a

Re: Test suit failures after upgrade to 2.13 (because IN no longer accepts a Java array)

Hey, I just checked and it doesn't seem as if any of the test cases use arrays with more than 1 element in them. It also gives the wrong results if I use an array with multiple values. On Tue, 17 May 2022 at 09:56, Николай Ижиков wrote: > Hello, Courtney. > > I’m able to reproduce y

Re: Test suit failures after upgrade to 2.13 (because IN no longer accepts a Java array)

15:24, Николай Ижиков <mailto:nizhi...@apache.org>> wrote: > Hello, Courtney. > > Can, you, please, send SQL table definition and example of query (java code > and SQL) that worked on 2.8 and start failing on 2.13. > > > This seems like a

Re: Test suit failures after upgrade to 2.13 (because IN no longer accepts a Java array)

QL) that worked on 2.8 and start failing on 2.13. > > > This seems like a regression, was this intentional? > > Looks like a bug to me. > Details of your schema and query can help in further investigation. > > > 10 мая 2022 г., в 10:14, Courtney Robinson > написал(а):

Re: Test suit failures after upgrade to 2.13 (because IN no longer accepts a Java array)

ion. > 10 мая 2022 г., в 10:14, Courtney Robinson написал(а): > > Hi all, > > We're looking to do a major upgrade from 2.8.0 to 2.13.0 > After the initial upgrade our test suite started failing (about 15% of tests > now fail). > No other change has been made other tha

Re: Test suit failures after upgrade to 2.13 (because IN no longer accepts a Java array)

the initial upgrade our test suite started failing (about 15% of > tests now fail). > No other change has been made other than the Ignite version number. > > org.apache.ignite.internal.processors.query.IgniteSQLException: General >> error: "class org.apache.ignite.IgniteExcepti

Re: Test suit failures after upgrade to 2.13 (because IN no longer accepts a Java array)

m 2.8.0 to 2.13.0 > After the initial upgrade our test suite started failing (about 15% of tests > now fail). > No other change has been made other than the Ignite version number. > > org.apache.ignite.internal.processors.query.IgniteSQLException: General > error: "class o

Test suit failures after upgrade to 2.13 (because IN no longer accepts a Java array)

Hi all, We're looking to do a major upgrade from 2.8.0 to 2.13.0 After the initial upgrade our test suite started failing (about 15% of tests now fail). No other change has been made other than the Ignite version number. org.apache.ignite.internal.processors.query.IgniteSQLException: General

test

Spread bets and CFDs are complex instruments and come with a high risk of losing money rapidly due to leverage. 66% of retail investor accounts lose money when spread betting and/or trading CFDs with this provider. You should consider whether you understand

Re: test

Test Passed - Denis On Wed, Nov 10, 2021 at 7:12 AM Veena Mithare wrote: > > -- > > > Spread bets and CFDs are complex instruments and come with a high risk of > losing money rapidly due to leverage. *66% of retail investor accounts > lose mone

test

Spread bets and CFDs are complex instruments and come with a high risk of losing money rapidly due to leverage. 66% of retail investor accounts lose money when spread betting and/or trading CFDs with this provider. You should consider whether you understand

Re: Unit test best practices

ast two nodes to simulate distributed environment (set IgniteInstanceName for this) * Reduce number of Ignite starts/stops for perf reasons: instead, create a new cache(s) for every test to isolate test data. * Optionally use something like TestContextLogger [1] [1] https://github.com/apache/ignit

Re: Unit test best practices

s that use actual DB provide more value, because you actually test that the whole system works. But they are slower and more resource-hungry. You can mock/fake Ignite - all APIs are interfaces (IIgnite, ICache, etc). On Thu, Apr 1, 2021 at 4:59 PM Kathryn Hogg wrote: > What is the best re

Unit test best practices

What is the best recommendations for automated tests of applications that use Ignite? On one hand you have Unit test purists that insist that you should be mocking data that is coming from Ignite. On the other hand, you have more practical people that say if you do that, you can't actually

Re: System.Collections.Generic.KeyNotFoundException: The given key was not present in the cache during load test with ignite 2.9.1

i/Apache.Ignite.Core.Cache.ICache-2.html#Apache_Ignite_Core_Cache_ICache_2_TryGet__0__1__ > > > On Mon, Feb 15, 2021 at 5:12 AM Ilya Kazakov > wrote: > >> Hello, Charlin! >> >> Could you show any reproducer, please? >> >> >> Thanks, Ilya! >> >> пт

Re: System.Collections.Generic.KeyNotFoundException: The given key was not present in the cache during load test with ignite 2.9.1

-- > Thanks, Ilya! > > пт, 12 февр. 2021 г. в 18:43, Charlin S : > >> Hi, >> I am getting below error while running load test with ignite 2.9.1 but >> ContainsKey is successful and thereafter Get by key is failed >> The given key was not present in the cache: &

Re: System.Collections.Generic.KeyNotFoundException: The given key was not present in the cache during load test with ignite 2.9.1

Hello, Charlin! Could you show any reproducer, please? Thanks, Ilya! пт, 12 февр. 2021 г. в 18:43, Charlin S : > Hi, > I am getting below error while running load test with ignite 2.9.1 but > ContainsKey is successful and thereafter Get by key is failed &g

System.Collections.Generic.KeyNotFoundException: The given key was not present in the cache during load test with ignite 2.9.1

Hi, I am getting below error while running load test with ignite 2.9.1 but ContainsKey is successful and thereafter Get by key is failed The given key was not present in the cache: TestModel:HH|E6661DD9C3@$@@$@@$@(null)@$@@$@(null)@$@System.Collections.Generic.KeyNotFoundException: The given key

Re: Feature request: method to test active connection in Ignite thin client

llo, >>>>> >>>>> I'm a new Ignite user, and with just a little bit of exposure, I'm >>>>> quite impressed with it -- it did not take me long to get a >>>>> single standalone remote node up and running and start using it as a >>>>>

Re: Feature request: method to test active connection in Ignite thin client

t;> I'm a new Ignite user, and with just a little bit of exposure, I'm >>>> quite impressed with it -- it did not take me long to get a >>>> single standalone remote node up and running and start using it as a >>>> durable memory key-value store. >>>> &g

Re: Feature request: method to test active connection in Ignite thin client

it as a durable memory key-value >>> store. >>> >>> I created a connection pool for ClientCache in Java, using Apache >>> Commons Pool 2. So far it's working well, but I had to fudge overriding >>> the commons-pool2 "validateObject()" method

Re: Feature request: method to test active connection in Ignite thin client

created a connection pool for ClientCache in Java, using Apache Commons >> Pool 2. So far it's working well, but I had to fudge overriding the >> commons-pool2 "validateObject()" method, which is a method to test that >> your pooled object is still alive and well:

Re: Feature request: method to test active connection in Ignite thin client

able memory key-value > store. > > I created a connection pool for ClientCache in Java, using Apache Commons > Pool 2. So far it's working well, but I had to fudge overriding the > commons-pool2 "validateObject()" method, which is a method to test that > your poo

Feature request: method to test active connection in Ignite thin client

Apache Commons Pool 2. So far it's working well, but I had to fudge overriding the commons-pool2 "validateObject()" method, which is a method to test that your pooled object is still alive and well: I used clientCache.getName().equals("MY_CACHE") as a test, but I have no id

Re: Ignite test takes several days

> Thank you for your reply. As mentioned earlier, I want to test ignite-core > with a new patch, so -DskipTests is not an option for me. What test suite > should I use if I just want to test ignite-core? > > > > On Tue, Sep 8, 2020 at 5:33 AM Petr Ivanov <mailto:mr.wei...@gm

Re: Ignite test takes several days

Hi, all Thank you for your reply. As mentioned earlier, I want to test ignite-core with a new patch, so -DskipTests is not an option for me. What test suite should I use if I just want to test ignite-core? On Tue, Sep 8, 2020 at 5:33 AM Petr Ivanov wrote: > Also, -DskipTests flag can be u

Re: Ignite test takes several days

d with -DskipTests. > > If you really want to run Ignite tests, you should run this test suite > against your PR: > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAll#all-projects > > <https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_

Re: Ignite test takes several days

Hello! You should never try to run all Ignite tests. They are not supposed to be run in that way. You should always build with -DskipTests. If you really want to run Ignite tests, you should run this test suite against your PR: https://ci.ignite.apache.org/buildConfiguration

Re: Ignite test takes several days

As per, it's configured to run for a very long time. Anyway, it is a part of IgnitePerformanceTestSuite which contains long-running performance tests and I believe they shouldn't be running for each commit. So, I think you can just disable this test suite. Evgenii пт, 28 авг. 2020 г. в 10:52

Re: Ignite test takes several days

Hi, I want to run all the tests. Actually I want to apply the patch for https://issues.apache.org/jira/browse/IGNITE-10959 to 2.8.1. I find that even for the original 2.8.1 source code, the test takes a long time. I think there must be an env or configuration issue. Do I need any special

Re: Ignite test takes several days

Hi, No, it's not normal. Do you really want to run all the tests locally, or you just want to build the project? If you want just to build it, I suggest skipping tests by using -Dmaven.*test*.*skip*=true flag. Evgenii чт, 27 авг. 2020 г. в 06:33, Cong Guo : > Hi, > > I try to build t

Ignite test takes several days

Hi, I try to build the ignite-core on my workstation. I use the original ignite-2.8.1 source package. The test, specifically GridCacheWriteBehindStoreLoadTest, has been running for several days. Is it normal? I run "mvn clean package" directly. Should I configure anything in advance? Thank you.

Test Mail

Re: TEST mail

ltiple times but no luck. > Anyone knows the issue? > > On Tue, Feb 25, 2020 at 10:45 PM Rick Alexander > wrote: > >> Test MAIL reply >> >> On Tue, Feb 25, 2020, 12:00 PM Prasad Bhalerao < >> prasadbhalerao1...@gmail.com> wrote: >> >>> >>>

Re: TEST mail

my mails with body contents are not showing up in ignite user list. Sent the same mail multiple times but no luck. Anyone knows the issue? On Tue, Feb 25, 2020 at 10:45 PM Rick Alexander wrote: > Test MAIL reply > > On Tue, Feb 25, 2020, 12:00 PM Prasad Bhalerao < > prasadbhalera

Re: TEST mail

Test MAIL reply On Tue, Feb 25, 2020, 12:00 PM Prasad Bhalerao wrote: > >

TEST mail

Re: Please test it and include in the next version if is possible: Modifications in rest-http module (Added JSF,jndi for jdbc/ignite and tunning for threads of jetty embedded)

the new internal case is: IGNITE-12518 -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Please test it and include in the next version if is possible: Modifications in rest-http module (Added JSF,jndi for jdbc/ignite and tunning for threads of jetty embedded)

Thanks Alexey, I make other change in the code for support root context for the webpage. (if is not present, ignite is a context root and ignite has /ignite context) GridJettyRestHandler.java

Re: Please test it and include in the next version if is possible: Modifications in rest-http module (Added JSF,jndi for jdbc/ignite and tunning for threads of jetty embedded)

Hi, mastercracker3d! The right way to change code is the following: 1. Create account in Apache Ignite JIRA https://issues.apache.org/jira/projects/IGNITE 2. Create issue in JIRA. 3. Prepare pull request. 4. Send e-mail on dev-list (see:

Please test it and include in the next version if is possible: Modifications in rest-http module (Added JSF,jndi for jdbc/ignite and tunning for threads of jetty embedded)

Hi community,I modified the Java Classes: GridJettyRestHandler and GridJettyRestProtocolIt's including support for JSF WebPages, auto load JNDI for JDBC/Ignite, Tunning for Thread of Jetty Embedded.Please remove old libraries of Jetty.The list of depencies are the

test subscribe

test subscribe -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: how to use bigbench test ignite performance

Hi, As I know Ignite provides its own benchmarks that used Yardstick framework. Documentation: https://apacheignite.readme.io/docs/perfomance-benchmarking yardstick: https://github.com/gridgain/yardstick In Ignite sources exists IgniteAbstractBenchmark class that could be used for creation

how to use bigbench test ignite performance

Just like the subject title,has anyone tested the Ignite performance by bigbench or other kind of benchmark util? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Test Ignite Client

Hi Humphrey, Consider forcing server mode on the client https://apacheignite.readme.io/docs/clients-vs-servers#section-forcing-server-mode-on-client-nodes. Another option is to enforce bean definition registration order. You could explicitly order configurations so that server bean gets

Re: Test Ignite Client

Hi Humphrey, Can you show the code? -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Test Ignite Client

Hello, I have the following question, I want to test my IgniteClient, which has it's own @Configuration file which has an igniteBean: Now I created a separate AppConfig for the testing (which Imports the AppConfig above from the client), and I want to start first a server node so the client

Re: Re: How the Ignite Service performance? When we test the CPU soon be occupied 100%

application. I not sure this is the best practice? Regards Aaron aa...@tophold.com From: Andrey Mashenkov Date: 2017-10-24 19:29 To: user; aaron Subject: Re: How the Ignite Service performance? When we test the CPU soon be occupied 100% Hi aaron, Can you make and share JFR profile [1

Re: How the Ignite Service performance? When we test the CPU soon be occupied 100%

Hi aaron, Can you make and share JFR profile [1] if it is still actual? [1] https://apacheignite.readme.io/docs/jvm-and-system-tuning#section-flightrecorder-settings -- Best regards, Andrey V. Mashenkov

Re: Jepsen test: Hazelcast vs Ignite

Hi Andrew, Yes, the community used Jepsen before and is planning to expand the coverage by this specific testing framework. -- Denis -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Jepsen test: Hazelcast vs Ignite

Hi, Just read on Jepsen test with Hazelcast: https://jepsen.io/analyses/hazelcast-3-8-3 Providing that Ignite have quite similar functionality as Hazelcast, Is there any plans to try the same tests with Apache Ignite (or Gridgain)? Seems like Gridgain team have at least one person able to run

Re: Streaming test

Jessie, If it's a preprocessing done on client side, then I think it should happen on application level. Do required preprocessing, convert to Ignite's data model and then do cache operations. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Streaming-test

答复: 答复: problems in test ignite PersistentStore

got it ,thank you Val, I got to have another try. 发件人: vkulichenko <valentin.kuliche...@gmail.com> 发送时间: 2017年8月19日 1:54:11 收件人: user@ignite.apache.org 主题: Re: 答复: problems in test ignite PersistentStore You don't see anything in /ssd folder, because you pr

Re: Streaming test

in context: http://apache-ignite-users. > 70518.x6.nabble.com/Streaming-test-tp14039p16310.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >

Re: Streaming test

is the same is in other systems. Servers store data, run services and computations, etc. while clients are only used to interact with the cluster. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Streaming-test-tp14039p16310.html Sent from the Apache Ignite

Re: 答复: problems in test ignite PersistentStore

in runtime anyway, so it should be done in XML as part of PersistentStoreConfiguration bean: -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/problems-in-test-ignite-PersistentStore-tp16244p16297.html Sent from the Apache Ignite Users ma

Re: Streaming test

supposed to be executed on > server > or client side? > > Can you give an example? > > -Val > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Streaming-test-tp14039p16270.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >

答复: problems in test ignite PersistentStore

127.0.0.1:47500..47502 after I changed my code and xml file，the test program can run normally.

Re: Streaming test

What does business logic do exactly? Is it supposed to be executed on server or client side? Can you give an example? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Streaming-test-tp14039p16270.html Sent from the Apache Ignite Users mailing list archive

problems in test ignite PersistentStore

hello guys: I'm trying to test the new feature PersistentStore, and got below questions: 1. streamer.addData() only support Nothing type input, how to make it support Int,String and others? here is my code: import java.util.List; import org.apache.ignite.Ignite; import

Re: Streaming test

y to suggest a solution. > > -Val > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Streaming-test-tp14039p16213.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >

Re: Streaming test

Can you describe the use case and what you want to achieve, step by step? I'll try to suggest a solution. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Streaming-test-tp14039p16213.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Streaming test

;> on the server, so it will obviously need all classes it works with. Am I >> missing something? >> >> Can you show the whole trace? >> >> -Val >> >> >> >> -- >> View this message in context: http://apache-ignite-users.705 >> 18.x6.nabble.com/Streaming-test-tp14039p16189.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > >

Re: Streaming test

Am I > missing something? > > Can you show the whole trace? > > -Val > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Streaming-test-tp14039p16189.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >

Re: Streaming test

/Streaming-test-tp14039p16189.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Streaming test

-SNAPSHOT-jar-with-dependencies.jar: ?] at org.apache.ignite.internal.marshaller.optimized.OptimizedMarshallerUt ils.classDescriptor(OptimizedMarshallerUtils.java:268) ~[sample-client:?] -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Streaming-test

Re: Streaming test

ce#init(). As I already > mentioned, this is causing the startup hang. You should move > IgniteAtomicLong creation out of init() method to avoid it. > > -Val > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Streaming-test-tp1

Re: Streaming test

l.java:63) Jessie On Wed, Aug 9, 2017 at 2:29 PM, vkulichenko <valentin.kuliche...@gmail.com> wrote: > I can't reproduce it, your project works fine for me. Can you attach thread > dumps? > > -Val > > > > -- > View this message in context: http://apache-ignite-use

Re: Streaming test

Jessie, What do you mean by "stuck"? Did you check thread dumps? Is it possible you have memory/GC issues? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Streaming-test-tp14039p16066.html Sent from the Apache Ignite Users mailing li

Re: Streaming test

>> >> >> -- >> View this message in context: http://apache-ignite-users.705 >> 18.x6.nabble.com/Streaming-test-tp14039p15646.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > >

Re: Streaming test

e > initialization step. > > -Val > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Streaming-test-tp14039p15646.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >

Re: Streaming test

Jessie, atomicLong() method will do this for you automatically. It either creates new instance or returns existing one. There is no need for separate initialization step. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Streaming-test-tp14039p15646.html

Re: Streaming test

Jessie, Ignite#atomicLong method will return existing instance if it is already initialized, so you actually don't need to manage this manually. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Streaming-test-tp14039p15525.html Sent from the Apache Ignite

Re: Streaming test

Thank you for running the test. If I need to initialize Atomic Seq, where shall I do it? Jessie On Fri, Jul 21, 2017 at 12:37 PM, vkulichenko <valentin.kuliche...@gmail.com > wrote: > I ran the test. Atomic sequence initialization should be moved out of > init() > becau

Re: Streaming test

I ran the test. Atomic sequence initialization should be moved out of init() because it is called synchronously with node start, and they wait for each other. After I do this, everything works fine. Although CSV file has only 348 and it gets loaded multiple times in a loop. Is there anything

Re: Streaming test

Hello there, please my test project. You can see 1) The initialization seem didn't finish 2) the streaming client stopped after a while. If you take out the Atomic sequence part, the stream start to work. Thank you for helping. Jessie -- View this message in context: http://apache-ignite

Re: Streaming test

Hi, Could you please share your test project? Thanks! -Dmitry. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Streaming-test-tp14039p14041.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Streaming test

this message in context: http://apache-ignite-users.70518.x6.nabble.com/Streaming-test-tp14039.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Error: Cannot open include file:'noost/test/unit_test.hpp'

Hi, I tried to build Ignite.sln. But I got Cannot open include file:'noost/test/unit_test.hpp' error. <http://apache-ignite-users.70518.x6.nabble.com/file/n11315/IgniteError.png> -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-Cannot-open-includ

Re: Ignite Cassandra AWS test framework

, than it's something wrong with you build or you probably used such command *mvn install -Dmaven.test.skip=true* to compile/package you distribution. The problem with *-Dmaven.test.skip=true *flag is that it completely skips all test artifacts creation (which you need). Just use slightly another

Re: Ignite Cassandra AWS test framework

Thank you Igor, unfortunately the issue I was referring to is still present in the documentation. Actually the AWS test deployment section <https://apacheignite-mix.readme.io/docs/aws-infrastructure-deployment> is still the same. I also tried running the deployment scripts in AWS w

Re: Ignite Cassandra AWS test framework

cumentation, but some files the documentation says >> I should modify are not in the test-package after I build ignite from >> source. >> >> Just to be clear, this is the link to the guide I am actually trying to >> follow: >> https://apacheignite-mix.readme.io/docs/

Re: Ignite Cassandra AWS test framework

Hi Val, No, that's not the issue. I would like to follow the AWS ignite-cassandra framework guide on the documentation, but some files the documentation says I should modify are not in the test-package after I build ignite from source. Just to be clear, this is the link to the guide I am

Ignite Cassandra AWS test framework

I am trying to evaluate Cassandra and Ignite following the AWS deployment guide in the documentation. I've built both Ignite 1.6 and 1.7 from source, but in both cases the test package generated misses the configuration file *bootstrap/aws/env.sh* I should modify according to the documentation

Re: Why doesn't the index be used in my test?

Hi Bob, If you put annotation on fields then need to use "CacheConfiguration.setIndexedTypes". But for Query Entity, you must discribe entiti in configuration (QueryEntity.setIndexes) without annotation. Please, look at [1] If it doesn't help, provide your query configuration. [1]:

Why doesn't the index be used in my test?

Hi everyone, I have a model Kc21, akc273 is its one String column . I create the index in this column, as the following: @QuerySqlField(index = true) private String akc273; Then I load data into cache from oracle, total 47535542 rows. I execute the sql query to get the

Re: Re: Some problems in test case which comparing sql query performance between Ignite and Oracle

g.setCacheStoreFactory(storeFactory); ccfg.setWriteThrough(true); cfg.setBackups(0); cfg.setMemoryMode(CacheMemoryMode.OFFHEAP_TIERED); cfg.setAtomicityMode(CacheAtomicityMode.ATOMIC); cfg.setCacheMode(CacheMode.PARTITIONED); To Yakov, I have not a real scenario, only test Ignite from simple sql q

Re: Some problems in test case which comparing sql query performance between Ignite and Oracle

Community going to > implement adding indexes on alive cache, but for now it is not possible. > > On Thu, Oct 20, 2016 at 12:10 PM, 胡永亮/Bob <hu...@neusoft.com> wrote: > >> Hi, everyone >> >> My test environment: Ignite cluster has 8 nodes, every nod

Re: Some problems in test case which comparing sql query performance between Ignite and Oracle

to another cache (with index) and drop this. Community going to implement adding indexes on alive cache, but for now it is not possible. On Thu, Oct 20, 2016 at 12:10 PM, 胡永亮/Bob <hu...@neusoft.com> wrote: > Hi, everyone > > My test environment: Ignite cluster has 8 nodes, every node ha

Re: Some problems in test case which comparing sql query performance between Ignite and Oracle

Bob, 1) Did you create index on Ignite cache? 2) Could you attach you cluster and cache configs? I also agree with Jörn Franke, that such simple query (no joins, simple "where condition") is not very suitable for benchmarking (unless all in your app you are using such queries a lot). --

Re: Some problems in test case which comparing sql query performance between Ignite and Oracle

. > On 20 Oct 2016, at 11:10, 胡永亮/Bob <hu...@neusoft.com> wrote: > > Hi, everyone > > My test environment: Ignite cluster has 8 nodes, every node has 8 cores > CPU and 30G memory. Their network has 1000M speed. > Oracle is deployed in the machine which has

Some problems in test case which comparing sql query performance between Ignite and Oracle

Hi, everyone My test environment: Ignite cluster has 8 nodes, every node has 8 cores CPU and 30G memory. Their network has 1000M speed. Oracle is deployed in the machine which has 32G memory and 8 cores CPU. My db table has 47535542 rows with 99 columns. When no index

test

test -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/test-tp8120.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: 答复: question about ignite benchmark test

://apache-ignite-users.70518.x6.nabble.com/question-about-ignite-benchmark-test-tp6737p6812.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

?????? Is there any test case for disaster tolerance ?

thank you very much, and I will try it ! -- -- ??: "Vladislav Pyatkov";<vldpyat...@gmail.com>; : 2016??8??5??(??) 7:24 ??: "user"<user@ignite.apache.org>; : Re: Is there any test case

Re: Is there any test case for disaster tolerance ?

ur answer, and I want to know that how the developers of > ignite test disaster tolerance ? > > > -- 原始邮件 -- > *发件人:* "Vladislav Pyatkov";<vldpyat...@gmail.com>; > *发送时间:* 2016年8月4日(星期四) 晚上6:13 > *收件人:* "user"<

Re?? Is there any test case for disaster tolerance ?

Thanks for your answer, and I want to know that how the developers of ignite test disaster tolerance ? -- -- ??: "Vladislav Pyatkov";<vldpyat...@gmail.com>; : 2016??8??4??(??) 6:13 ??: "user"<user@i

答复: question about ignite benchmark test

ignite benchmark test Hi Kevin, This is the number of keys involved into PUT or GET operation. If there is 1 key, then IgniteCache.get() or IgniteCache.put() operation was used. If there are more keys, then we benchmarked IgniteCache.getAll() or IgniteCache.putAll() operations. On Thu, Aug 4

Re: question about ignite benchmark test

for the big cache in off heap, say over 20G per node and hundreds of gigabytes or over 1T in total ? Thanks, -Jason -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/question-about-ignite-benchmark-test-tp6737p6753.html Sent from the Apache Ignite Users mailing list

Re: Is there any test case for disaster tolerance ?

Hello, Ignite has some test on yardstick framework (in module ignite-yardstick) and documentation of how to use it here https://github.com/gridgain/yardstick and here https://github.com/apacheignite/yardstick-ignite. For checking disaster tolerance you can use any test from the module (ignite

  1   2   >