dbTalk Databases Forums  

[Info-Ingres] IMA query duration

comp.databases.ingres comp.databases.ingres


Discuss [Info-Ingres] IMA query duration in the comp.databases.ingres forum.



Reply
 
Thread Tools Display Modes
  #11  
Old   
Ingres Forums
 
Posts: n/a

Default Re: [Info-Ingres] IMA query duration - 08-11-2010 , 02:23 PM






Hi Gerhard

I will send you the presentation via e-mail.

BR
Frédéric


--
fba

Reply With Quote
  #12  
Old   
Ingres Forums
 
Posts: n/a

Default Re: [Info-Ingres] IMA query duration - 08-12-2010 , 03:28 AM






Frederic,

I have sent you an e-mail asking for the source code from that
presentation. You have either ignored it, or did not receive it at all.
I think presentation was brilliant, but it would be really great if
source code is available somewhere so we do not have to write it again
and again...
It would be really great if you paste the code somewhere. 'Pastebin.com
- #1 paste tool since 2002!' (http://ingres.pastebin.com) is the place
where #ingres people paste their code snippets. So I recommend it
instead of thousands of other similar places.


--
dejan

Reply With Quote
  #13  
Old   
Ingres Forums
 
Posts: n/a

Default Re: [Info-Ingres] IMA query duration - 08-12-2010 , 04:52 AM



@Dejan

Well... I just got back from a 3-week holiday, so I haven't processed
all my e-mails yet, only the urgent ones. I remember seeing an e-mail
wrt to my presentation. :-) I'll try to do that as soon as I can.

I think it would be much better of course to have a trace point to log
long queries (and long locks...)?
Maybe I'll just have to join the code sprint next year. ;-)

@Mason
Wouldn't it be better to have a whole new trace point rather than risk
breaking sc924?


--
fba

Reply With Quote
  #14  
Old   
Paul Mason
 
Posts: n/a

Default Re: [Info-Ingres] IMA query duration - 08-12-2010 , 05:57 AM



I think the risk to sc924 would be minimal and in any case the code that
actually outputs the query text is already called from lots of places
(it's part of a generic error output routine in uleformat.c) and
triggers on other error messages not just the sc924 - so it's already
shared in that sense.

I also think the benefit of re-using this is that if something changes -
e.g. I just did a fix to stop the text getting truncated in some
circumstances - then it only has to be changed in one place.

Paul

Quote:
-----Original Message-----
From: info-ingres-bounces (AT) kettleriver...ting (DOT) com [mailto:info-
ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Ingres Forums
Sent: 12 August 2010 10:52
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: Re: [Info-Ingres] IMA query duration


@Dejan

Well... I just got back from a 3-week holiday, so I haven't processed
all my e-mails yet, only the urgent ones. I remember seeing an e-mail
wrt to my presentation. :-) I'll try to do that as soon as I can.

I think it would be much better of course to have a trace point to log
long queries (and long locks...)?
Maybe I'll just have to join the code sprint next year. ;-)

@Mason
Wouldn't it be better to have a whole new trace point rather than risk
breaking sc924?


--
fba

Reply With Quote
  #15  
Old   
Ingres Forums
 
Posts: n/a

Default Re: [Info-Ingres] IMA query duration - 08-12-2010 , 06:36 AM



fba;33471 Wrote:
Quote:
Hi Gerhard

I will send you the presentation via e-mail.

BR
Frédéric
Thanks a lot, have received it, it's very interesting.

Regards
Gerhard


--
gerhard.hofmann (AT) planat (DOT) de
------------------------------------------------------------------------
gerhard.hofmann (AT) planat (DOT) de's Profile: http://community.ingres.com/forum/member.php?userid=857
View this thread: http://community.ingres.com/forum/sh...ad.php?t=12397

Reply With Quote
  #16  
Old   
Robert Allely
 
Posts: n/a

Default Re: [Info-Ingres] IMA query duration - 09-13-2010 , 05:14 PM



I originally raised this question, and then I coded some OpenROAD objects to do a similar thing to the ESQLC process mentioned below.

The queries that have been there a while are stored in an array, they are written out to a table when its decided that they are slow (number of seconds since first seen).
If they are in LOCK state the blocking lock is found , using the usual ima method.
It took a few hours to do but I already had all the ima sql setup , I just needed to manage the array of continued queries.

-Robert


-----Original Message-----
From: info-ingres-bounces (AT) kettleriver...ting (DOT) com [mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Gerhard Hofmann
Sent: Wednesday, 11 August 2010 10:23 p.m.
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: Re: [Info-Ingres] IMA query duration

On 11 Aug., 11:57, Ingres Forums <info-
ing... (AT) kettleriverconsulting (DOT) com> wrote:
Quote:
Hi

I have used a similar approach.
An ESQLC-program with a loop that inserts the running queries in a
table. I keep the queries running longer than a particular time interval
in the table, so I can run reports on it later.
I apply the same approach to get queries locking other queries longer
than a specified time.
I presented my approach on the IUA in London last June, so my
presentation should be available on the IUA website.

PostgreSQL has a parameter in the configuration file that says to log
queries taking longer than a number of milliseconds
(log_min_duration_statement). It would certainly be nice to have
something like that in Ingres. It wouldn't probably be very difficult
adding an parameter to the SC930 trace point (query recording) to
specify a number of milliseconds. ;-)

Best regards
Frédéric

Unfortunately not here:
http://www.iua.org.uk/confindex.htm

Could you provide an alternative download link of the presentation?

TIA
Gerhard
_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres
Confidentiality/Privilege Notice:
This communication is confidential and may be legally privileged. If you are not the intended recipient please delete the message and notify the sender at Ports of Auckland Limited. Any use, disclosure, copying, distribution or retention of this communication is strictly prohibited.

Reply With Quote
  #17  
Old   
Roy Hann
 
Posts: n/a

Default Re: [Info-Ingres] IMA query duration - 09-14-2010 , 02:09 AM



Robert Allely wrote:

Quote:
I originally raised this question, and then I coded some OpenROAD
objects to do a similar thing to the ESQLC process mentioned below.

The queries that have been there a while are stored in an array,
they are written out to a table when its decided that they are slow
number of seconds since first seen).
If they are in LOCK state the blocking lock is found , using the
usual ima method.
It took a few hours to do but I already had all the ima sql setup,
I just needed to manage the array of continued queries.
This is a useful and informative exercise, but if you need results and
development time is limited, you could also take a look at DBAnalyzer
from http://www.dmt.com for Ingres.

As well as shipping with a number of useful alarms and trend monitoring
tools, it also includes a performance database that you can query to
create your own alarms. The performance database is extremely useful
because it has already computed many of the rates/deltas you'd be
interested in.

--
Roy

UK Ingres User Association Conference 2011 will be on Tuesday June 7 2011.
Put the date in your diary today.

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.