Thanks Mark.
What is the design considerations to break large files into 4M chunk rather than storing the large file directly?
Thanks,
Guang
From: Mark Kirkwood <mark.kirkwood@xxxxxxxxxxxxxxx>
To: Guang Yang <yguang01@xxxxxxxxx>
Cc: "ceph-users@xxxxxxxxxxxxxx" <ceph-users@xxxxxxxxxxxxxx>
Sent: Monday, August 19, 2013 5:18 PM
Subject: Re: Usage pattern and design of Ceph
On 19/08/13 18:17, Guang Yang wrote:
> 3. Some industry research shows that one issue of file system is the
> metadata-to-data ratio, in terms of both access and storage, and some
> technic uses the mechanism to combine small files to large physical
> files to reduce the ratio (Haystack for example), if we want to use ceph
> to store photos, should this be a concern as Ceph use one physical file
> per object?
If you use Ceph as a pure object store, and get and put data via the
basic rados api then sure, one client data object will be stored in one
Ceph 'object'. However if you use rados gateway (S3 or Swift look-alike
api) then each client data object will be broken up into chunks at the
rados level (typically 4M sized chunks).
Regards
Mark
_______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
