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:
Why are you using index type FULLTEXT for a Long data type? That should be
SORTED I think.
> On 13 Nov 2020, at 09:57, Lieuwe wrote:
>
> Gangaiah - this will reproduce what I am seeing:
>
> #pragma GCC diagnostic ignored "-Wdeprecated-declarations"
> #include
> #include
> #include
>
>
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
Hello!
Can you please provide all rows of "EXPLAIN SELECT ... WHERE A=?"
query?
Regards,
--
Ilya Kasnacheev
чт, 12 нояб. 2020 г. в 20:04, Lieuwe :
> 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
Hi Lieuwe,
To understand this in detail, please give more details like how you are
calculating TPS and code snippet for each one where you are doing
put/get/cursor.hasNext().
Regards,
Gangaiah
-
Thanks and Regards,
Gangaiah
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
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
