> > For de-duplication to perform well you need to be able to fit the > > de- > > dup table in memory. Is a good rule-of-thumb for needed RAM > > Size=(pool > > capacity/avg block size)*270 bytes? Or perhaps it's > > Size/expected_dedup_ratio? > > For now, the rule of thumb is 3G ram for every 1TB of unique data, > including > snapshots and vdev's. > > After a system is running, I don't know how/if you can measure current > mem usage, to gauge the results of your own predictions.
3 gigs? Last I checked it was a little more than 1GB, perhaps 2 if you have small files. Vennlige hilsener / Best regards roy -- Roy Sigurd Karlsbakk (+47) 97542685 r...@karlsbakk.net http://blogg.karlsbakk.net/ -- I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med fremmed opprinnelse. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk. _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
