Re: Scalability of OSTree

On Fri, Dec 4, 2015, at 01:07 PM, Jasper St. Pierre wrote:
I think that makes sense, but since a "repo" in our / xdg-app's case
might contain thousands if not hundreds of thousands of branches (some
of our internal talk has been assuming stuff like ~100 new branches a
week), it seems like OSTree isn't designed to work well for the scale
we need.

I don't understand branches on that scale; are you doing a branch-per
release and using them like tags?  (If OSTree had tags, but note you
can kind of simulate this using the ostree.version metadata and
the fetcher better understands them now)

There's always multiple repositories too remember.

I think we'll work on an independent system for shipping content to
users. Thanks.

That may make sense, but it's hard for me to talk about this
without having *some* idea of what the content is and how
it's modeled.

At least if you're doing a new format, you'll likely want binary-level
deltas, and I think our work on
is reusable.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]