Perhaps a DAOS inside can be the solution

I had a problem with growing Domino databases and didn’t have the option to turn DAOS. And I thought how could this problem be solved if I did some database design. What is the problem today with large Domino databases or large attachments today?

1. Large or many Attachments makes the database slow
2. Opening documents become slow.

DAOS solves these issues by extracting the attachment out of the database and creating a file with a hash name to get a single copy solution, Very clever. The hashing of files solution original developed by and MIT professor named Ron Rivest. He was one of the founders of RSA (the R is from his name ) 

I tough if you could have a DAOS like solution stored inside a single NSF file then you could benefit from this when if you server didn’t have DAOS enabled. And also if you did a local replica.

If the attachments were extracted from the actual document like they are in DAOS, I belive that the performance would increase. This because the attachments are only touched in they are needed and not every time the document fetched like today. But this is just a wish from me ๐Ÿ˜‰  

It will be interesting to see what new features IBM will implement into the NSF container in the next ODS version. So the Domino NSF container can show that it’s the largest NoSQL database what I know of.

Have a great NSF Day!!

  1. Large or many Attachments makes the database slow

    What part of the database will become slow and what is the reason for it?

  2. I have experienced performance problems with large attachments because if you have i.e. have an agent navigating thru a view with documents with large attachments from ร  notes client you will probably get timeouts. This is because if you don’t use the viewentry navigator you need to open each document when the document is retrieved.


Leave a Comment

NOTE - You can use these HTML tags and attributes:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>