Subject | Re: excessive network traffic [LONG] |
---|---|
Author | Aage Johansen |
Post date | 2001-01-25T20:34:09Z |
Art,
I wonder if 1518 is a max block size. Perhaps a large block needs to be
split into manageable chunks.
I've also noticed _a lot of activity_ when accessing a database over
dialup and would be interested to know how to lessen the burden. I got
some improvement by making certain that queries were prepared just once.
(You aren't using TTables, are you?)
Regards,
Aage J.
You wrote:
...
4. // Is this query generated by the BDE?
select rdb$owner_name, rdb$relation_name, rdb$system_flag,
rdb$view_blr, rdb$relation_id from rdb$relations
where rdb$relation_name = 'alarminfo'
returns 1518+1518+1518+1246+170+
1518+1518+1518+1246+
1518+1518+1518+1450
(=17774) bytes
The "stuttering" of the value 1518 makes me wonder if the BDE (or possibly
gds32) is attempting a query; timing out; and then re-sending. OTOH, the
client doesn't resend. Could the server be looking for an ACK and
re-sending if one doesn't come through?
...
I wonder if 1518 is a max block size. Perhaps a large block needs to be
split into manageable chunks.
I've also noticed _a lot of activity_ when accessing a database over
dialup and would be interested to know how to lessen the burden. I got
some improvement by making certain that queries were prepared just once.
(You aren't using TTables, are you?)
Regards,
Aage J.
You wrote:
...
4. // Is this query generated by the BDE?
select rdb$owner_name, rdb$relation_name, rdb$system_flag,
rdb$view_blr, rdb$relation_id from rdb$relations
where rdb$relation_name = 'alarminfo'
returns 1518+1518+1518+1246+170+
1518+1518+1518+1246+
1518+1518+1518+1450
(=17774) bytes
The "stuttering" of the value 1518 makes me wonder if the BDE (or possibly
gds32) is attempting a query; timing out; and then re-sending. OTOH, the
client doesn't resend. Could the server be looking for an ACK and
re-sending if one doesn't come through?
...