Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qfs use cases #241

Open
jeromew opened this issue Dec 10, 2019 · 1 comment
Open

qfs use cases #241

jeromew opened this issue Dec 10, 2019 · 1 comment

Comments

@jeromew
Copy link

jeromew commented Dec 10, 2019

Hello,

I understand that qfs was developed over the years to replace hdfs with better characteristics for the mapReduce use case over very large files.

I am looking into qfs for building a clustered fs out of low end commodity vps (e.g. vps with 1Go Ram, 1 vCPU, 20Go disk) and am wondering if the following use cases are possible and the limitations that I should expect

  • store a lot of small images
  • store one big sqlite file spanning across the cluster and interact with it

Thanks for your help (I hope it is ok to ask this question here on the issue tracker. Do not hesitate to tell me if there is a better place for asking such questions)

@mikeov
Copy link
Contributor

mikeov commented Dec 15, 2019

Chunk header size is 16KiB. Each non empty file would have at least 1 chunk, therefore disk storage overhead for files less than 64MB would be minimum 16KiB with replication 1. Replication obviously acts as multiplier. With Reed Solomon (RS) encoding the overhead depends on the file and stripe size as recovery stripes are padded. For example 1 byte file with 6+3 RS would occupy (16KiB + 1) * 4. The minimum support stripe size is 4KiB, the default 64KiB.

Meta server memory utilization in bytes: 72 + 104 + file_name_length.

Support for random writes is limited with replicated / non RS files. With RS files only sequential write is supported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants