I have an installation in which terminal monitor has a distinct pause of about 12seconds between starting and displaying a prompt.

I have run a sysmod on iidbdb.

I have confirmed there is no page overflow on iiprotect or iiqrytext.

strace -f sql iidbdb stalls at the poll...

socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 3
fcntl(3, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
connect(3, {sa_family=AF_INET, sin_port=htons(50677), sin_addr=inet_addr("127.0.0.1")}, 16) = -1 EINPROGRESS (Operation now in progress)
poll([{fd=3, events=POLLOUT, revents=POLLOUT}], 1, 2147483607) = 1
getpeername(3, {sa_family=AF_INET, sin_port=htons(50677), sin_addr=inet_addr("127.0.0.1")}, [5761845549825261584]) = 0
setsockopt(3, SOL_TCP, TCP_NODELAY, [1], 4) = 0
setsockopt(3, SOL_SOCKET, SO_KEEPALIVE, [1], 4) = 0
poll([{fd=3, events=POLLOUT, revents=POLLOUT}], 1, 2147483597) = 1
write(3, "\0\0\0\0l\0\0\0l\0\0\0QRCG\0\0\0\0atlantic.cts".. ., 116) = 116
write(3, "\0\0\0\0\210\0\0\0<\0\0\0\6\0\0\0PACG\0\0\0\0C\0\ 0\0\0"..., 144) = 144
poll(

Does anyone know what its polling for and why it may be waiting?

Martin Bowes

Do you have set trace point qe90?

I had to switch that off on our Ingres 10 testing because of slowness.


--
jruffer

Ingres Forums wrote:

QE90 is known to slow queries; you shouldn't expect to use it in
production unless you have power to burn.

I'd use something like trace point SC930 to discover where the
performance problems are, then maybe look at the query plans, and then
depending on those, use QE90 to see if the actual costs diverge
wildly from the estimates.

--
Roy

UK Ingres User Association Conference 2011 will be on Tuesday June 7 2011.
Register at http://www.regonline.co.uk/ukiua2011

On Mar 29, 2011, at 8:29 AM, Roy Hann wrote:


Indeed. QE90 has to call the OS for the cpu time at entry and
exit of every query plan node, for every row. It's very expensive.

I've long meant to do a QE90 variant that only tracks rowcounts
(and maybe DIO) without doing the full time accounting. Sounds
like another sprint project!

Karl

Hi J,

No, I only use qe90 for specific query analysis.

In the end we simply stopped and restarted the installation and for whatever reason the problem has dissapeared.

Marty

-----Original Message-----
From: Ingres Forums [mailto:info-ingres (AT) kettleriverconsulting (DOT) com]
Sent: 29 March 2011 12:52
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: Re: [Info-Ingres] slow terminal monitor startup


Do you have set trace point qe90?

I had to switch that off on our Ingres 10 testing because of slowness.


--
jruffer


_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres