Hi all, I am writing a simple C++ dll which uses the mapi interface to connect to MonetDB. The query itself runs extremely fast which is fantastic. I did notice that the mapi_connect() takes approximately 1 second to connect on my machine on a local socket. Is there anyway to improve this connection latency? I can't unfortunately use a connection pool or keep the connection open due to the design of the calling application. Best regards, Matthew Russell
Hi On 22/01/14 15:29, Matthew Russell wrote:
Hi all,
I am writing a simple C++ dll which uses the mapi interface to connect to MonetDB.
The query itself runs extremely fast which is fantastic. I did notice that the mapi_connect() takes approximately 1 second to connect on my machine on a local socket.
Is there anyway to improve this connection latency? I can't unfortunately use a connection pool or keep the connection open due to the design of the calling application. Assuming you connect using SQL, then most likely not. The user session environment has to be set up first, which calls for quite some administrative tasks.
To further be of advice, we should know more about the application setup/specifics. regards, Martin
Best regards,
Matthew Russell
_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
Hi, I am actually trying to integrate MonetDB with an old SQL Server application using SQL CLR integartion. The CLR function calls a C++ dll which uses the mapi interface. Since I can't hold state in the CLR, I have to reconnect to MonetDB for each call. There may also be concurrent calls from SQL Server, which means I think I need a new connection context for each call. Best Regards Matthew ________________________________________ Hi On 22/01/14 15:29, Matthew Russell wrote:
Hi all,
I am writing a simple C++ dll which uses the mapi interface to connect to MonetDB.
The query itself runs extremely fast which is fantastic. I did notice that the mapi_connect() takes approximately 1 second to connect on my machine on a local socket.
Is there anyway to improve this connection latency? I can't unfortunately use a connection pool or keep the connection open due to the design of the calling application. Assuming you connect using SQL, then most likely not. The user session environment has to be set up first, which calls for quite some administrative tasks.
To further be of advice, we should know more about the application setup/specifics. regards, Martin
Best regards,
Matthew Russell
_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
Hi This sounds like a pack of hacks ;) On 22/01/14 16:21, Matthew Russell wrote:
Hi,
I am actually trying to integrate MonetDB with an old SQL Server application using SQL CLR integartion. The CLR function calls a C++ dll which uses the mapi interface. Since I can't hold state in the CLR, I have to reconnect to MonetDB for each call.
There may also be concurrent calls from SQL Server, which means I think I need a new connection context for each call.
Best Regards Matthew
________________________________________ Hi
On 22/01/14 15:29, Matthew Russell wrote:
Hi all,
I am writing a simple C++ dll which uses the mapi interface to connect to MonetDB.
The query itself runs extremely fast which is fantastic. I did notice that the mapi_connect() takes approximately 1 second to connect on my machine on a local socket.
Is there anyway to improve this connection latency? I can't unfortunately use a connection pool or keep the connection open due to the design of the calling application. Assuming you connect using SQL, then most likely not. The user session environment has to be set up first, which calls for quite some administrative tasks.
To further be of advice, we should know more about the application setup/specifics.
regards, Martin
Best regards,
Matthew Russell
_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
_______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list _______________________________________________ users-list mailing list users-list@monetdb.org https://www.monetdb.org/mailman/listinfo/users-list
On 22-01-2014 14:29:51 +0000, Matthew Russell wrote:
Hi all,
I am writing a simple C++ dll which uses the mapi interface to connect to MonetDB.
The query itself runs extremely fast which is fantastic. I did notice that the mapi_connect() takes approximately 1 second to connect on my machine on a local socket.
1 second sounds like some foobared DNS lookup problem. A connect surely should succeed way faster than 1 second. Out of curiosity (and to try and reduce the problem) does a connection through JDBC have the same latency? (Can use jdbcclient to easily test it.) Fabian
Hi Fabian,
Thanks for your help. Using the string "localhost" was introducing the latency compared to using "127.0.0.1".
The latency is down to just a few milliseconds, so it must have been a DNS issue.
Best regards and thanks,
Matthew
________________________________________
From: users-list
Hi all,
I am writing a simple C++ dll which uses the mapi interface to connect to MonetDB.
The query itself runs extremely fast which is fantastic. I did notice that the mapi_connect() takes approximately 1 second to connect on my machine on a local socket.
1 second sounds like some foobared DNS lookup problem. A connect surely should succeed way faster than 1 second. Out of curiosity (and to try and reduce the problem) does a connection through JDBC have the same latency? (Can use jdbcclient to easily test it.) Fabian
participants (3)
-
Fabian Groffen -
Martin Kersten -
Matthew Russell