I was very happy when I heard that DAOS would result in typically 40 - 60% space savings.
I have installed DAOS on a production server and have “only” saved about 15 % space. Don’t get me wrong I am happy for the 15%, I was just wondering if it is only my setup or if other admins are getting better results. Here are my metrics:
approx. 100 mail users
the mail folder is 22 GB in size
the entire data directory is 52,8 GB
after activating DAOS:
data directory is 44,6 GB
I used the following command
load compact -c -daos on -n -v -ZU
I had previously activated LZ1 compression (-ZU) on most of the databases
So, what about you, what where your space savings after activating DAOS
As far as I can remember I had already activated data and design compression. I had definatly already activated LZ1 attachment compression (for most of the databases). I have also created a very easy way for users to copy Emails into project databases so that they can send a link instead of forwarding a mail - I can now assume that this has paid off :o)
From the comments that I have read I can only assume that I had a pretty optimised system to begin with :o)
The amount of data moved to DAOS is directly related to the amount of attachment data you have. The amount of savings using DAOS is directly related to the amount of redundant data you have.
There are two elements you need to look at with DAOS
How much data separation did you get? (nsf size reduction… attachments moved to DAOS storage)
and
2), how much duplication did DAOS eliminate
Both are very important. You don’t break down the separation.
The 40-60 percent numbers are pretty typical for early deployers that I have talke with who enabled both compression AND DAOS on mail type servers.
I would verify that attachments are correctly being stored in DAOS by doing a
sh dir -daos
on the domino console. Do the number of attachments stored in DAOS seem to be reasonable ?
The attachments are being placed in the DAOS store (I started with a documentation database and checked that files where being placed in the directory - I also checked that the physical size of the DB was getting smaller).
I assume that I had an already optimised for size system (LZ1 attachment compression, compression activated) and therefor my data davings where “only” 15% - I think that the extra 15% is great :o)
The reported 40-60% includes Document Data Compression, Design Compression and DAOS. At IBM we reported about a ~22% savings with DAOS. Following is data about Document Data Compression (8.0.1+). Have you enabled this also? Please note that you will also need to compact with the -c to compress existing data. Instructions below the graphic.
Available NOW in Domino 8.01
Compression of Rich Text (e.g mail messages)
Works for client (local) and server databases
Quota relief!
Enabled using a database property or Compact
Compact dbname.nsf –v << enable
Compact dbname.nsf –V << disable
Use in conjunction with compact –c option to compress existing data documents
We saw ~34% disk space reclaimed when enabling Document Data Compression and Design Compression. When you’re talking Terabytes of data, the savings was HUGE. I’d highly recommend anyone on version 8.0.1 to enable the two compression technologies. The clients can still be on R6. We have not seen any significant performance impact either. To me, this one is a no-brainer!
We do not use mail but we have several attachment-rich applications. I just completed implementing DAOS and total disk space was reduced 25%. LZ1, DAOS, no design or document compression.