Develop benchmarks for real-world filesystem loads

[humphd]

We'd like to be able to measure how real-world filesystems work in MakeDrive, specifically to understand how various backend providers are performing, in order to tune sync parameters, etc.

Doing this will mean figuring out what typical, and common edge-case scenarios look like for Webmaker users (e.g., how many dirs, how many files, what types of files, what size of files, etc).

I'm going to assign this to @gideonthomas and expect that he'll reach out to @jbuck, @simonwex, @Pomax, and others as he tries to develop a set of common filesystem configurations and tests.

Some things to consider:

• inclusion of legacy data from our current apps (thimble, popcorn maker, x-ray goggles, etc.) since we can extract real-world info about what our users are doing now
• special consideration for the appmaker use case, and what component authors will need
• discussions with various Webmaker tool people for input about how and what they'll store in MakeDrive.

[simonwex]

/me subscribes

[sedge]

@gideonthomas This is probably worth looking at again. We're almost at a point where other services can plug into this.

[humphd]

A good first step here would be to use realistic filesystem layouts from the Mobile Appmaker work (bundle + images + ???). I'm hoping @thisandagain can help us here, and maybe we can get some zip files that show the kinds of common (and edge case) filesystem uses Mobile Appmaker will have. I'm particularly interested in knowing: number of files, size of files, and being able to write automated tests of various kinds that work on those data sets.

[alicoding]

@humphd can you comment on this bug if we want to get to this in this milestone or move this out for now since Webmaker app still in development

[humphd]

We still need word on if/when we're going to see image assets in MakeDrive for Mobile Webmaker. That will help determine a lot here.

[alicoding]

duplicate of #455