+------+-------------------------------------------------------------------------------------------------------------------------------------------------+
| usec | statement |
+======+=================================================================================================================================================+
: : ult_pipe":str, 10:int); #[1] (0) QLOGdefineNaive 1 <- 2 3 15 :
| 78 | sqlcatalog.create_table("sys":str, "rmt_tbl8":str, 0x7f22dc193190:ptr, 0:int); #[2] (0) SQLcreate_table 13 <- 8 10 12 6 |
| 1 | sql.exportOperation(); #[3] (0) mvc_export_operation_wrap 14 |
+------+————————————————————————————————————————————————————————————————————————+
And this is the trace result of the older version which takes 4msec
+------+-------------------------------------------------------------------------------------------------------------------------------------------------+
| usec | statement |
+======+=================================================================================================================================================+
: : ult_pipe":str, 10:int); :
| 666 | sqlcatalog.create_table("sys":str, "rmt_tbl9":str, nil:ptr, 0:int); |
| 103 | sql.exportOperation(); |
+------+-------------------------------------------------------------------------------------------------------------------------------------------------+
maybe you can prefix the queries with TRACE to look deeper into the execution of these queries to see where the time was spent?
Probably not, but I ‘m trying to figure out why in versions prior to Aug.2018 I ‘m getting this:
operation successful
sql:0.000 opt:0.359 run:0.473 clk:4.634 ms
While in versions after Aug. 2018 I have:
operation successful
sql:0.000 opt:0.068 run:0.057 clk:87.766 ms
Hi,
I am trying to develop a Python client which sends queries to different Monetdb servers and transfers the results between them using the remote tables functionalities.
I’ve seen than my main overhead is execution of CREATE REMOTE TABLE statement. It requires 70-90msec so in cases with many transfers and fast and small queries this
makes a difference. After looking at some older versions I’ve seen that the creation of a remote table was very fast before August 2018 (this is when authentication added).
Is there any hint on this? Could the. authentication strategy change in someway so that it runs faster or is it possible to select among different authentication methods for the remote tables?
Jennie
_______________________________________________
users-list mailing list
users-list@monetdb.orghttps://www.monetdb.org/mailman/listinfo/users-list
_______________________________________________
users-list mailing list
users-list@monetdb.orghttps://www.monetdb.org/mailman/listinfo/users-list
_______________________________________________
users-list mailing list
users-list@monetdb.orghttps://www.monetdb.org/mailman/listinfo/users-list