![]() ![]() ![]() but if the request ends, I cannot see it anymore, or the "plan" shows jsut thw word "query", iirc. I found that I can see the query plan only for really long queries, if I switch fastly to the request tab of the VDB details, click refresh and hit "plan" button. So, how can teiid (or the as, or the server where's running, or else) help me in this debug job? I know there are tons of different reasons, for this, and I'm willing to create the best possible setup to spot what is not working well. so I don't know if it's a good comparison. On windows, thought, it seems less different (faster). Selecting more fields from the vdb (or *) only makes thing worse. Even very simple queries need 4-5 seconds to get the response, while mysql odbc is blasing fast. python with pypyodbc, on linux and windowsĪnd anywhere, in linux server, odbc/mysql is much faster than odbc/postgres (to teiid). php, both using odbc_connect and pdo, on linux and windows php framework (code igniter) with odbc database odbc query tool ( ODBC Query Tool download | ) same win7, odbc to teiid I did a few tests, with everything I have at hand: ![]() I also tested an identical odbc "mysql" dsn on the same server, which connects to a mysql db (the same also used as model in the teiid vdb), but I get very slow results when those results come from the "teiid" odbc dsn.ĭriver = /usr/lib/i386-linux-gnu/odbc/libmyodbc.so My ideal "test" client is a linux webserver running apache/php using odbc to get data from teiid.ĭriver = /usr/lib/i386-linux-gnu/odbc/psqlodbcw.so I am trying to debug a very slow odbc connection to teiid: I'm pretty sure it is due to some client factor but I wish to be sure (ie: learn) what can I do on teiid side to debug what/when is happening exactly in teiid as a response from the client query. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |