Opened 17 years ago
Last modified 17 years ago
#1167 assigned defect
Kapa + region causes long delay over remote X connections.
| Reported by: | Michael Wood-Vasey | Owned by: | eugene |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | DVO | Version: | unspecified |
| Severity: | minor | Keywords: | |
| Cc: |
Description
Why does 'region' over a remote X connection take minutes with Kapa enabled and seconds with '$KAPA = -noX'? The larger the DVO database, the longer it takes. It's not drawing anything to the screen, why does it take so long?
I'll take a few pointers of files to look at if I can be helpful in tracing this down. Reading through Ohana/src/opihi/cmd.astro/region.c didn't seemed fine, but I didn't trace down to the next level of all of the commands called from that.
This is becoming more important as larger and larger DVO database are assembled and so kept on remote machines instead of just shipped to the machine I'm working on.

with some testing, we've determined that this problem is caused by the initiation of the kapa connection. specifically, there seems to be a long lag between when the client completes its connection and when the server 'select' statement (in KapaServerWait) returns.
but only for slow connections...