On Aug 3, 2010, at 1:31 PM, Barry Jaspan wrote:
> Is this considered a bug? I thought the trace translator was supposed to be
> enableable at any level of the translator stack, including multiple levels,
> so you could debug calls across any translator.
That's correct. What happened here is tha
On Tue, Aug 3, 2010 at 3:49 PM, Jeff Darcy wrote:
> It turns out that
> when the trace translator is enabled in the client volfile, it becomes
> the lowest and thus the one that's mounted . . .
Is this considered a bug? I thought the trace translator was supposed to be
enableable at any level o
On Aug 3, 2010, at 14:49, Jeff Darcy wrote:
> On 08/03/2010 10:24 AM, Major Hayden wrote:
>> Initial test with my normal client volfile:
>> Client volfile: http://pastie.org/1072935
>> untar: 32.999s
>> removal: 4.540s
>>
>> Second test with debug/trace translator enabled:
>> Client volfile:
On 08/03/2010 10:24 AM, Major Hayden wrote:
> Initial test with my normal client volfile:
> Client volfile: http://pastie.org/1072935
> untar: 32.999s
> removal: 4.540s
>
> Second test with debug/trace translator enabled:
> Client volfile: http://pastie.org/1072951
> untar: 6.077s
> re
This has stumped me beyond belief. I'm actually getting *much better* small
file performance with debug/trace added into the client-side volfile than
without it. Here's what I did to test it:
1) Downloaded latest.tar.gz (current Wordpress tarball from wordpress.org)
2) tar xzf latest.tar.g
