Hi Agneeswaran,
Thats a great thing to hear. I'm going to change the default value to
something more appropriate.
Let us know if there are any other issues you are facing.
Best Regards,
Igor
On Mon, Jul 11, 2016 at 8:53 PM, Agneeswaran <
agneeswaran.ponnuraman...@nielsen.com> wrote:
> Hi Igor
Hi Igor,
The solution works perfectly fine.It completes in ~12 seconds ( before ~4
minutes ).
Thanks for your support.
With regards,
Agneeswaran
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Performance-issue-on-Ignite-ODBC-API-tp5908p6212.html
Sent from the
Hi, Agneeswaran,
As I said, internally ODBC driver retrieves data in pages, not one by one.
It only returns one row to user by call but it retrieve data from the remote
node in pages, not one by one.
However, I have checked now and found out that by some reason default
page size is very small. Yo
Hi Igor,
We have checked our configuration details and we suspect that the
performance degradation is with the
SQLFetch(stmt); This issue happens only with the client server model not
with the odbc-example.
Lets say,
Database has Row count as 10 and column count as 5.
Please see the following c
Hi Igor,
Thanks for the detailed information.
As suggested, Will check our configuration and code.
With regards,
Agneeswaran
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Performance-issue-on-Ignite-ODBC-API-tp5908p6007.html
Sent from the Apache Ignite Users
Agneeswaran,
I have tested and profiled ODBC using data from odbc-example and I can see
that 1 million rows, 3 string columns each retrieved by ODBC in ~8 seconds
on
first run, and in less than ~5 seconds on second run.
Actually, ODBC driver always retrieving data by pages of size 1024 rows so
it
Agneeswaran,
Let me have a look. I will profile the code and will tell you results.
Best Regards,
Igor
On Wed, Jun 29, 2016 at 4:48 PM, Agneeswaran <
agneeswaran.ponnuraman...@nielsen.com> wrote:
> Hi Igor,
>
> Using Java API we can fetch the data within ~5 seconds but in C++ it took
> ~4
> min
Hi Igor,
Using Java API we can fetch the data within ~5 seconds but in C++ it took ~4
minutes.
Will it possible to fetch the data, let say 500-1000 records at once.
Could you please suggest us.
Thanks,
Agneeswaran
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.
Hi Igor,
Thanks for the information. Will try to implement as suggested.
Will reach out to you if we have any queries.
With regards,
Agneeswaran
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Performance-issue-on-Ignite-ODBC-API-tp5908p5927.html
Sent from the
Agneeswaran,
Here you can find details on how to use SQL queries from Java at [1].
Also, do you really have 7 string columns? Try using the matching types,
this way you can avoid type cast overhead.
[1] - https://apacheignite.readme.io/docs/sql-queries
Best Regards,
Igor
On Mon, Jun 27, 2016 at
Hi Igor,
Yes, it takes more than 15 minutes for ~70 thousand rows.
We are running on C++ with Linux. We never tried with java API.
Could you please pass us some links to use Java API.
Thanks in advance,
With regards,
Agneeswaran
--
View this message in context:
http://apache-ignite-users.70
Hi, Agneeswaran,
So, what is the problem? Does this code work slow? Can you compare to the
same query performed using Java API and say the difference?
Best Regards,
Igor
On Mon, Jun 27, 2016 at 11:55 AM, Agneeswaran <
agneeswaran.ponnuraman...@nielsen.com> wrote:
> Hi Team,
>
> We are facing pe
12 matches
Mail list logo
