On 2013-05-13, at 17:22, Daniel Phillips daniel.raymond.phill...@gmail.com
wrote:
Hi Ted,
You said:
...any advantage of decoupling the front/back end
is nullified, since fsync(2) requires a temporal coupling
After after pondering it for a while, I realized that is not
completely
Hi Dave,
Thanks for the catch - I should indeed have noted that modified
dbench was used for this benchmark, thus amplifying Tux3's advantage
in delete performance. This literary oversight does not make the
results any less interesting: we beat Tmpfs on that particular load.
Beating tmpfs at
also interesting information... Study of 2,047 papers on PubMed finds
that two-thirds of retracted papers were down to scientific
misconduct, not error
On Fri, May 10, 2013 at 11:12 PM, Daniel Phillips
daniel.raymond.phill...@gmail.com wrote:
Hi Dave,
Thanks for the catch - I should indeed
On Fri, May 10, 2013 at 11:12:27PM -0700, Daniel Phillips wrote:
Hi Dave,
Thanks for the catch - I should indeed have noted that modified
dbench was used for this benchmark, thus amplifying Tux3's advantage
in delete performance.
Dropping fsync() does a lot more than amplify Tux3's
