We believe we've resolved at least some of the problems we were seeing with the skiplist backend. The performance problem may just have been due to memory overcommitment on our production server (we increased the memory).
We've resolved the looping problem; it was a slight problem with one process updating header information and another process never reading that information. We're now running it in production and things seem to be working well; we'll let people know if we see any other problems. Larry Date: Tue, 26 Feb 2002 12:41:58 -0500 From: Walter Wong <[EMAIL PROTECTED]> [...] There also is bug that we can't reproduce that will result in the skiplist getting into a loop. "Luckily" this has only happened with seen state and only happens to one user every four to eight hours. Our plans are to look at making things more efficient -- possibly by separating the log from the data and so having two files and not just one. We're looking at throwing additional debugging code in to try to find out how it gets into the loop, or at worst throwing in a hack that if it detects the loop to break it automatically. So, right now, I wouldn't recommend switching your production system over to it. Walter
