@michaelcahill, this change gives me about 1-2% on medium-btree wtperf runs on the AWS benchmarking machine.

I think a possible down-side is btree->appending could be a hot cache line if a workload alternates between appending and inserting randomly, but on the other hand, it should never be set for read-only workloads.