Re: xfs: does mkfs.xfs require fancy switches to get decent performance? (was Tux3 Report: How fast can we fsync?)

2015-05-13 Thread Daniel Phillips
On 05/13/2015 04:31 AM, Daniel Phillips wrote: Let me be the first to catch that arithmetic error Let's say our delta size is 400MB (typical under load) and we leave a nice big gap of 112 MB after flushing each one. Let's say we do two thousand of those before deciding that we have enough

Re: xfs: does mkfs.xfs require fancy switches to get decent performance? (was Tux3 Report: How fast can we fsync?)

2015-05-13 Thread Daniel Phillips
On 05/13/2015 06:08 AM, Mike Galbraith wrote: On Wed, 2015-05-13 at 04:31 -0700, Daniel Phillips wrote: Third possibility: build from our repository, as Mike did. Sorry about that folks. I've lost all interest, it won't happen again. Thanks for your valuable contribution. Now we are seeing

Re: Blurt code in Github

2015-05-13 Thread Elifarley Callado Coelho Cruz
Where can I see the torture test results ? Maybe it would be good to use Wercker ( which is free - http://wercker.com/ ) to make sure we always have binaries automatically built for every new commit. Elifarley Cruz Professional info: http://linkd.in/elifarley | https://github.com/elifarley |

Re: xfs: does mkfs.xfs require fancy switches to get decent performance? (was Tux3 Report: How fast can we fsync?)

2015-05-13 Thread Martin Steigerwald
Am Mittwoch, 13. Mai 2015, 13:38:24 schrieb Daniel Phillips: On Wednesday, May 13, 2015 1:25:38 PM PDT, Martin Steigerwald wrote: Am Mittwoch, 13. Mai 2015, 12:37:41 schrieb Daniel Phillips: On 05/13/2015 12:09 PM, Martin Steigerwald wrote: ... Daniel, if you want to change the process

Re: Tux3 Report: How fast can we fail?

2015-05-13 Thread Daniel Phillips
Addendum to that post... On 05/12/2015 10:46 AM, I wrote: ...For example, we currently overestimate the cost of a rewrite because we would need to go poking around in btrees to do that more accurately. Fixing that will be quite a bit of work... Ah no, I was wrong about that, it will not be a

Re: Blurt code in Github

2015-05-13 Thread Elifarley Callado Coelho Cruz
Using port 80 would be easier for me, any chance of configuring Apache to map that? Maybe I could do that for you. And what is the URL for Tux3's Worcker page ? Thanks! Elifarley Cruz Professional info: http://linkd.in/elifarley | https://github.com/elifarley |

Re: Blurt code in Github

2015-05-13 Thread Daniel Phillips
On 05/13/2015 07:07 AM, Elifarley Callado Coelho Cruz wrote: Where can I see the torture test results ? You mean, http://buildbot.tux3.org:8010/ ? I am not as familiar with it as I should be. Maybe it would be good to use Wercker ( which is free - http://wercker.com/ ) to make sure we