You would only get SIGINT if you run your application in a shell and ctrl-c
it right? Can you not 'wait' on a key press and stop ignite properly
instead?
I looked at the same issue recently and I wouldn't expect ignite to do
anything that isn't documented - even if it does it now, it may not do
Why are you using index type FULLTEXT for a Long data type? That should be
SORTED I think.
As I said - I used the example shipped with ignite as a starting point. I
changed it to SORTED and it looks better indeed. Scenario 4 now runs at
about 7K TPS.
--
Sent from:
Ilya:
0: jdbc:ignite:thin://127.0.0.1/> EXPLAIN SELECT A, B, C, D FROM TEST.TEST
WHERE A = 1;
++
| PLAN |
++
| SELECT
__Z0.A AS __C0_0,
__Z0.B AS __C0_1,
__Z0.C AS __C0_2,
__Z0.D AS __C0_3
Gangaiah - this will reproduce what I am seeing:
#pragma GCC diagnostic ignored "-Wdeprecated-declarations"
#include
#include
#include
#define CACHE_SIZE 10
#define CHRONO_MS std::chrono::duration_cast
struct DataObject
{
int64_t A, B, C;
ignite::Guid D;
};
namespace
I wonder if anyone can shed some light on the Apache Ignite performance I am
seeing.
I am running a single node & have a very simple CacheConfiguration
consisting of 4 fields.
The program is very much like the put-get-example code shipped with Ignite &
I am doing a few tests to see how fast (how
