| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Questions about XFS |
| From: | Steve Bergman <sbergman27@xxxxxxxxx> |
| Date: | Tue, 11 Jun 2013 16:43:11 -0500 |
| Cc: | Ric Wheeler <rwheeler@xxxxxxxxxx>, Stefan Ring <stefanrin@xxxxxxxxx>, Linux fs XFS <xfs@xxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XvBSb1meqwoLToI5VY1j7xyQDmiCxmQa5IUtIKfjRak=; b=VwXqLibfjzsb5Wt+A1fH+zo3m+ytkBDyLNxhLBvALQLp+acPqdpMgHL0Re5tT1bGzF E68z4m+ZIxmZf/faSEGEP4YCqDt93WJlYDsRGxe4gB1SowGOnw/1Aqkta6yFQpogzxNo ImXy52dD6LHhStB5OIwfQtyxo5OFhfx52uiuGIc9j0zxSsrD18+sl/VEyaM1klQQi9vW faouR2dK1WE+JczTFF6mccqE4ZAU02xkcsYHGKQKoWMDtNhLsrsnj+WrejSFoJmdgVBj uA4wqTGCuzaY4SXuY1v96Td/I8/bxpVKMJNc5AglY2G0t9tHRXShziObkJvZ3TNlV/jr 3+Zg== |
| In-reply-to: | <20130611210312.GN29338@dastard> |
| References: | <loom.20130611T112155-970@xxxxxxxxxxxxxx> <51B72D3D.5010206@xxxxxxxxxx> <CAO9HMNGjdikgX+_434aGVJ2NAJ0hxDNLo+Vsa46GH3psXr4sKQ@xxxxxxxxxxxxxx> <51B75C39.3030306@xxxxxxxxxx> <CAAxjCEyne63XH1Uk6_7jzjaxDbsSopO9E+=6oo3xE=PvjBFcjA@xxxxxxxxxxxxxx> <51B75EF7.40801@xxxxxxxxxx> <CAO9HMNEk1qNVGzM+a052O1y0nm3-cxqM17BGWBZDc1byfWTa7w@xxxxxxxxxxxxxx> <20130611210312.GN29338@dastard> |
> I get it. You want a pony, and you don't want to pay anything for it. Hi Dave, Not at all. I don't mind incurring a performance penalty in that LV. Ext3 performance is quite acceptable, with the exception of a single maintenance operation which I perform periodically (which can be quite slow, indeed, on the larger files. Very intensive random writes.) Fortunately, the filesystem intensive part of that operation occurs in its own work directory. The files in that directory are just temporary work files. And at the end of the processing, the resulting files get copied back to the main data directory tree. XFS performs extremely well for this operation. For about a dozen years, I've been using Ext3 for the whole thing, and the resiliency has been much more than just adequate. (If I needed more, I'd mount ext3 data=journal; I can't imagine mounting synchronously.) But for this new server, and probably future ones, I'll be using Ext3 for the permanent data, and XFS for the work directory. It makes a huge difference for that one operation, and leverages the strengths of both filesystems to yield something more appropriate for the workload than either one alone. As Ted is fond of noting, one of Linux's greatest strengths is the variety of filesystems it offers. And sometimes filesystem performance just doesn't matter. -Steve |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 1/9] xfs: don't emit v5 superblock warnings on write, Ben Myers |
|---|---|
| Next by Date: | Re: Questions about XFS, Dave Chinner |
| Previous by Thread: | Re: Questions about XFS, Dave Chinner |
| Next by Thread: | Re: Questions about XFS, Ben Myers |
| Indexes: | [Date] [Thread] [Top] [All Lists] |