Forum

Kognitio Console issues, advice, etc.
Contributor
Offline
Posts: 184
Joined: Wed May 29, 2013 2:10 pm
Location: Bracknell

How can I make Console faster connected to loaded system?

by MikeAtkinson » Wed Jun 05, 2013 8:06 am

I'm running Kognitio Console on a large heavily loaded system and it locks up for several minutes when connecting, sometimes opening menus is slow as well.
Reply with quote Top
Contributor
Offline
Posts: 184
Joined: Wed May 29, 2013 2:10 pm
Location: Bracknell

Re: How can I make Console faster connected to loaded system

by MikeAtkinson » Wed Jun 05, 2013 8:42 am

When Console is connected to very large Kognitio Analytic Platform system (many thousands of tables and views spread over hundreds of schemas), heavily congested systems or is connected to systems over long latency links, Console might run slowly and /or lock up.

Console has a default configuration optimised for moderately used medium size systems with low communication latency. If that is not the case there are several configuration options that may be changed to improve things.

General: “Open database metadata tree on connection”

With this option unticked the system’s metadata tree is not initially expanded and only a minimum of metadata is requested from the server on connection. Mostly these are explain statements used to discover which facilities are available. After a delay more metadata is loaded.

General:Metadata: “Load column data on connection”

If ticked the metadata for each column for each table and view visible to the user is loaded. This can be slow if the user can see many thousands of tables. Having preloaded column data is useful for displaying entity diagrams and relationship diagrams.

Untick for a large decrease in the time to preload metadata; this will lead to a longer delay in expanding tables and views in the metadata and in displaying entity and relationship diagrams.

General:Metadata: “Load schemas on connection”

When this is ticked the visible tables, views and scripts within each schema visible to the user will be preloaded into the metadata tree.

Untick for a large decrease in the time to preload metadata; this will lead to a longer delay in expanding schemas in the metadata tree and in displaying entity and relationship diagrams. As table and view names are not known they will not be syntax highlighted within scripts, expand the schema(s) you are using to syntax highlight table/view names within scripts.

General:Metadata: “use prepared statements (since 7.2.1)”

Console may use prepared statements when supported by the Kognitio database (i.e. for version 7.2.1 and above). Creating the prepared statements is performed on the UI thread, while running them is done on a background thread. If a long running query is on the background thread is may block creating a prepared statement and hence block the UI, leading to grey windows and an unresponsive Console.

Untick for no blocking at the expense of a small extra load on the Kognitio database (queries need to be compiled each time they are run instead of just once) and a slightly longer query time (due to the time taken for compilation).

General:Metadata: “Metadata updates”

Do not tick these options. They cause repeated metadata queries which may be useful on lightly loaded systems to keep metadata synched to changes made by other users. In general use they would put unnecessary load on the database.

SQL:Dialog Options: “Use explain to only enable valid options”

When ticked Console uses explain statements to determine which tables and views are visible to a user and which SQL statements can be run. If a menu option cannot be run or a Macro is not available to the user then it is greyed out.

Untick for faster initial display of menus; subsequent display of a menu that has already been seen will always be fast.

SQL: “Automatically resize results to fit”

When ticked, for scripts and ad-hoc queries the resultset table columns are resized to fit the data width and the row height is resized for multiline text. This is quite slow for tables with thousands of rows, as each cell’s size needs to be determined. This leads to a delay between the end of the query and the resultset table being displayed.

If this option is unticked then scripts will run faster and ad-hoc queries will show their resultsets faster. It is then possible to resize the resultset using the “Resize to fit” pop-up menu option for the table.

Scripting: "Monitor long running queries"

When ticked queries that take longer than 10 seconds will have their status monitored every 10 seconds.

This will put an extra load on the Kognitio database.
Reply with quote Top

Who is online

Users browsing this forum: No registered users and 1 guest

cron