Ramblings from the bit bucket

A colleague was describing a performance issue encountered by a customer that eventually led to increasing the number of Ingres Net processes (often referred to as iigcc or comsvr). During installation, the number of comsvr configured to start defaults to 1 and it seems there it will remain in this age of set-and-forget. The topic of configuration defaults is huge and emotive and best left for others to discuss.

Going back to my colleague’s description, the point that came out of the discussion was that although there are IMA objects to show connections through the comsvr it would be useful to have objects that showed data throughput. My response was yes, it would be useful to have data throughput and to their surprise was the fact that there were objects already gathering that information probably since Ingres 2.6.

So in this brief post here is a redefined ima_gcc_info table registration that includes data_in and data_out, cumulative counts, expressed in KB and msgs_in and msgs_out, also cumulative counts.

I’ve only tried this on Ingres 2006 so please be careful if trying it on earlier versions.

drop table ima_gcc_info;
\p\g
register table ima_gcc_info (
net_server, varchar(64) not null not default
is 'SERVER',
inbound_max varchar(20) not null not default
is 'exp.gcf.gcc.ib_max',
inbound_current varchar(20) not null not default
is 'exp.gcf.gcc.ib_conn_count',
outbound_max varchar(20) not null not default
is 'exp.gcf.gcc.ob_max',
outbound_current varchar(20) not null not default
is 'exp.gcf.gcc.ob_conn_count',
data_in integer4 not null not default
is 'exp.gcf.gcc.data_in',
data_out integer4 not null not default
is 'exp.gcf.gcc.data_out',
msgs_in integer4 not null not default
is 'exp.gcf.gcc.msgs_in',
msgs_out integer4 not null not default
is 'exp.gcf.gcc.msgs_out'
) as import from 'tables'
with dbms = IMA,
structure = sortkeyed,
key = (net_server);
\p\g
grant select on ima_gcc_info to public with grant option;
\p\g