Edward Ned Harvey writes:
> > If you consider the extreme bias... If the system would never give up
> > metadata in cache until all the cached data were gone... Then it would be
> > similar to the current primarycache=metadata, except that the system would
> > be willing to cache data too, wh
Let me throw two cents into the mix here.
Background: I have probably 8 different ZFS boxes, BYO using SMC
chassis. The standard config now looks like such:
- CSE847-E26-1400LPB main chassis, X8DTH-iF board, dual X5670 CPUs, 96G
RAM (some have 144G)
- Intel X520 dual-10G card
- 2 LSI 9211-8i co
On Thu, Jun 2 at 20:49, Erik Trimble wrote:
Nope. In terms of actual, obtainable IOPS, a 7200RPM drive isn't
going to be able to do more than 200 under ideal conditions, and
should be able to manage 50 under anything other than the
pedantically worst-case situation. That's only about a 50% dev
On Fri, Jun 3, 2011 at 11:22 AM, Paul Kraus wrote:
> So is there a way to read these real I/Ops numbers ?
>
> iostat is reporting 600-800 I/Ops peak (1 second sample) for these
> 7200 RPM SATA drives. If the drives are doing aggregation, then how to
> tell what is really going on ?
I've always as
On Thu, Jun 2, 2011 at 11:49 PM, Erik Trimble wrote:
> On 6/2/2011 5:12 PM, Jens Elkner wrote:
>>
>> On Wed, Jun 01, 2011 at 06:17:08PM -0700, Erik Trimble wrote:
>>>
>>> On Wed, 2011-06-01 at 12:54 -0400, Paul Kraus wrote:
>>
>>> Here's how you calculate (average) how long a random IOPs takes:
>>
Edward Ned Harvey writes:
> Based on observed behavior measuring performance of dedup, I would say, some
> chunk of data and its associated metadata seem have approximately the same
> "warmness" in the cache. So when the data gets evicted, the associated
> metadata tends to be evicted too. S
