This repository has been archived!

This IPFS-related repository has been archived, and all issues are therefore frozen. If you want to ask a question or open/continue a discussion related to this repo, please visit the official IPFS forums.

We archive repos for one or more of the following reasons:

• Code or content is unmaintained, and therefore might be broken
• Content is outdated, and therefore may mislead readers
• Code or content evolved into something else and/or has lived on in a different place
• The repository or project is not active in general

Please note that in order to keep the primary IPFS GitHub org tidy, most archived repos are moved into the ipfs-inactive org.

If you feel this repo should not be archived (or portions of it should be moved to a non-archived repo), please reach out and let us know. Archiving can always be reversed if needed.

---

fs-stress-test

IPFS Stress tests

This repo will stress test IPFS filesystem capabilities.

Table of Contents

Background

The target goals are:

1. pass simple (1GB+) randomized tests
2. pass medium (1TB+) randomized tests
3. pass various real workloads:

• lots of docs
• containers and VMs
• videos
• DBs

4. pass large (1PB+) randomized tests

(Today we're at 1.)

Install

Simply clone this repository.

git clone https://github.com/ipfs/fs-stress-test

Installing deps

You may have to install deps. Will fix this soon (auto-install with ipfs).

go get -u github.com/ipfs/go-ipfs/cmd/ipfs
go get -u github.com/jbenet/go-random-files/random-files

Usage

Running Tests

make test

Contribute

Feel free to join in. All welcome. Open an issue!

This repository falls under the IPFS Code of Conduct.

Want to hack on IPFS?

License

Copyright (c) 2016 Juan Batiz-Benet