<<< Chronological >>> Author Index    Subject Index <<< Threads >>>

Re: tcp-conn hang at end of "server...low priority"

  • To: "Wilfried Woeber, UniVie/ACOnet" < >
  • From: Marten Terpstra < >
  • Date: Wed, 23 Nov 1994 20:51:13 +0100

"Wilfried Woeber, UniVie/ACOnet" woeber@localhost writes
 *   Dear DB-folks!
 *   
 *   My whois client seems to have problems in closing the TCP connection to
 *   the server at the end of a "more specifics" query that puts the server
 *   into "low priority mode".
 *   
 *   Looking at the output, it seems that I get all the information I should
 *   be getting (in the sequence in which it was loaded into the DB). 
 *   Then my server just hangs. Has anybody else seen this before?
 * 
 *   I never have seen problems (even with long output lists) which don't
 *   put the server in low-priority mode.
 *   
 *   Anything that I may be doing wrong?

Nothing wrong Wilfried, just impatient ;-) You indeed received what
you expected, but that was only the network objects. It was trying to
find the route objects for you next. Because of a lack of tree like
structure in the routes (no "assignment chain") this means the
database software has to check a lot of routes to see if they are more
specific and this is slow. And yes, it can be really slow for routes
right now.

The solution is sort of half done. I have implemented a way to fake a
tree structure in any classless index. This would speed up these
lookups by a lot. However, the implementation currently only works for
read-only database, ie databases that are not continuously updated,
but the ones that are copied once every so often and only indexed
(like what we do with the MERIT and INTERNIC databases). There are a
few modifications needed to make it work for "updatable" databases
which are on my list.

-Marten



  • Post To The List:
<<< Chronological >>> Author    Subject <<< Threads >>>