On 12/07/2012 04:14 PM, Theodore Ts'o wrote:
On Fri, Dec 07, 2012 at 02:30:19PM -0500, Steven Rostedt wrote:
How is this similar? By adding this bit, we removed incentive from a
group of developers that have the means to fix the real issue at hand
(the performance problem with ext4). Thus, it means that they have a work
around that's good enough for them, but the rest of us suffer.
That assumes that there **is** a way to claw back the performance
loss, and Chris Mason has demonstrated the performance hit exists with
xfs as well (950 MB/s vs. 400 MB/s; that's more than a factor of two).
Sometimes, you have to make the engineering tradeoffs. That's why
we're engineers, for goodness sakes. Sometimes, it's just not
possible to square the circle.
Keep in mind that no one has tried to retune or adjust XFS (or other file
systems) for this workload.
I don't believe that the technique of forcing people who need that
performance to suffer in order to induce them to try to engineer a
solution which may or may not exist is really the best or fairest way
to go about things.
The proposed solution will not ship in any enterprise distro. Google, I assume,
would require some specific non-normal user access permission.
That means that this solution will not be usable by the vast majority of users,
so it is clear that we do need to work on fixing the performance at the root
instead of plastering over the behaviour.
ric
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
