On Apr 3, 2008, at 14:43, dormando wrote:
I listed most of my own (ideas, I guess) on that along with the
1.3.0 release announcement. With flagrant musts and must'n'ts.
Wouldn't kill us to at least review what parts of the docs are
inconsistent with the server, laying them out on the list, or just
heavyhandedly deciding they differences are meaningless and updating
the docs.
I guess the bigger deal is to make stats work. Trond's apparently
already fixed the syscall performance issues, although we have not
verified if there are raw CPU regressions or the like (also detailed
in my release notes).
Yeah, the reduced syscall change is in. He says the numbers are the
same between the two protocols as of that change.
I don't think it'd be very hard to contrive a test that would at
least give us a feel as to whether it's faster or slower. Pretty much
anything that could run for five minutes and do the ``same thing''
would work if we just looked at the user time it used. Probably not
considerably less effort than using a profiler, though.
But yeah, the 1.3.0 series is open for minor changes. You don't have
to do them yourself if you're busy though, since it was me who put
it out as such :)
Nah, but I trust my tests to report when something goes wrong, so I'd
like to keep it going. I don't mind fixing stuff, either.
--
Dustin Sallings
