et == Erik Trimble erik.trim...@oracle.com writes:
et No, you're reading that blog right - dedup is on a per-pool
et basis.
The way I'm reading that blog is that deduped data is expaned in the
ARC.
pgpozjcLXZlNV.pgp
Description: PGP signature
Miles Nordin wrote:
et == Erik Trimble erik.trim...@oracle.com writes:
et No, you're reading that blog right - dedup is on a per-pool
et basis.
The way I'm reading that blog is that deduped data is expaned in the
ARC.
What I think is being done is this: for pool A and
I am currently doing research on how much memory ZFS should have for a storage
server.
I came across this blog
http://constantin.glez.de/blog/2010/04/ten-ways-easily-improve-oracle-solaris-zfs-filesystem-performance
It recommends that for every TB of storage you have you want 1GB of RAM just
On Wed, 19 May 2010, Deon Cui wrote:
http://constantin.glez.de/blog/2010/04/ten-ways-easily-improve-oracle-solaris-zfs-filesystem-performance
It recommends that for every TB of storage you have you want 1GB of
RAM just for the metadata.
Interesting conclusion.
Is this really the case that
- Deon Cui deon@gmail.com skrev:
I am currently doing research on how much memory ZFS should have for a
storage server.
I came across this blog
http://constantin.glez.de/blog/2010/04/ten-ways-easily-improve-oracle-solaris-zfs-filesystem-performance
It recommends that for every
Bob Friesenhahn wrote:
On Wed, 19 May 2010, Deon Cui wrote:
http://constantin.glez.de/blog/2010/04/ten-ways-easily-improve-oracle-solaris-zfs-filesystem-performance
It recommends that for every TB of storage you have you want 1GB of
RAM just for the metadata.
Interesting conclusion.
et == Erik Trimble erik.trim...@oracle.com writes:
et frequently-accessed files from multiple VMs are in fact
et identical, and thus with dedup, you'd only need to store one
et copy in the cache.
although counterintuitive I thought this wasn't part of the initial
release. Maybe I'm
Miles Nordin wrote:
et == Erik Trimble erik.trim...@oracle.com writes:
et frequently-accessed files from multiple VMs are in fact
et identical, and thus with dedup, you'd only need to store one
et copy in the cache.
although counterintuitive I thought this wasn't part
