Well I believe the attachments are in the same database file as the documents. So a huge amount of large attachments may causes some performance loss just due to the I/O and seeking. CouchDB doesn't cache anything itself and relies on the filesystem so it's performance can be IO bound.
As to if the CouchDB could handle the data, I would assume yes. If you are concerned about all the image data slowing it down you could use the documents in CouchDB to maintain metadata and a relative path to the image file and maintain the attachments on the filesystem manually with some middleware code and a static file server (nginx or something). I personally don't have any experience using CouchDB with a lot of attachment data or really a huge amount of data. It's be a great database for my fun projects though. On Fri, Jul 27, 2012 at 9:50 AM, Ajay Pawaskar <[email protected]>wrote: > Hi, > > Any suggestions > > Thx, > Ajay. > > -----Original Message----- > From: Ajay Pawaskar [mailto:[email protected]] > Sent: Thursday, July 19, 2012 3:44 PM > To: [email protected] > Subject: Data Size > > Hi > > I am Using Couch DB with .net Application. > > I want to store the Image Data in couchDB. > > my current Image Data is nearly 1TB [from another app]. > > Is it good to go with couch for this amount of data... as I am going to > add new images from my app as well. > > I am concern about how much time it will take to Insert/Retrieve > Image[Attachment]. > > > > Thx, > > Ajay. > > > > -- “The limits of language are the limits of one's world. “ - Ludwig von Wittgenstein "Water is fluid, soft and yielding. But water will wear away rock, which is rigid and cannot yield. As a rule, whatever is fluid, soft and yielding will overcome whatever is rigid and hard. This is another paradox: what is soft is strong." - Lao-Tzu
