>Hi,
> When a connection is made to a database in my Ingres 2 installation I
[quoted text clipped - 5 lines]
>Running sysmod and optimizedb hasn't seemed to help the 'problem'.
>Should I be concerned about this?
Ingres does a bunch of reads out of iidbpriv; a read for a
(user, grant-type, database) key and another with a blank
database name, for "user" = the real user, the group specified
if any, public, and the role specified if any. It also does
another, similar pair of reads for every role in the system,
I think. (That's in case of "set role" in the session.)
So it will always do at least 4 reads and possibly many more.
All of these are fully keyed unique record reads, though, and
none should do table scans, so the total size of iidbpriv should
not matter all that much. I'm guessing that either your
2K buffer cache is under-configured, or Ingres is being too
quick to throw away cached pages when iidbdb is closed.
Try this: open a terminal monitor session to iidbdb and let it
just sit there. Does that make connections go any faster?
If so, that might be the simplest workaround.
Karl
>Hi,
> When a connection is made to a database in my Ingres 2 installation I
[quoted text clipped - 5 lines]
>Running sysmod and optimizedb hasn't seemed to help the 'problem'.
>Should I be concerned about this?
Ingres does a bunch of reads out of iidbpriv; a read for a
(user, grant-type, database) key and another with a blank
database name, for "user" = the real user, the group specified
if any, public, and the role specified if any. It also does
another, similar pair of reads for every role in the system,
I think. (That's in case of "set role" in the session.)
So it will always do at least 4 reads and possibly many more.
All of these are fully keyed unique record reads, though, and
none should do table scans, so the total size of iidbpriv should
not matter all that much. I'm guessing that either your
2K buffer cache is under-configured, or Ingres is being too
quick to throw away cached pages when iidbdb is closed.
Try this: open a terminal monitor session to iidbdb and let it
just sit there. Does that make connections go any faster?
If so, that might be the simplest workaround.
Karl
William - 30 Aug 2006 21:55 GMT
> Ingres does a bunch of reads out of iidbpriv; a read for a
> (user, grant-type, database) key and another with a blank
[quoted text clipped - 3 lines]
> I think. (That's in case of "set role" in the session.)
> So it will always do at least 4 reads and possibly many more.
I have305 roles defined so maybe that's part of the problem.
> Try this: open a terminal monitor session to iidbdb and let it
> just sit there. Does that make connections go any faster?
> If so, that might be the simplest workaround.
Running a test with sql connecting to iidbdb in the backround speeds up
database connections by 39% :-)