# Testground examples with DID's a nodes spin up + profiling

**URL:** <https://discuss.ipfs.tech/t/testground-examples-with-dids-a-nodes-spin-up-profiling/14206>\
**Category:** Testground\
**Created:** [May 12, 2022, 6:02pm UTC](https://discuss.ipfs.tech/t/testground-examples-with-dids-a-nodes-spin-up-profiling/14206 "2022-05-12T18:02:44Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![forgondolin](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/forgondolin/32/4079_2.png) [@forgondolin](https://discuss.ipfs.tech/u/forgondolin)\
**Post date:** [May 12, 2022, 6:02pm UTC](https://discuss.ipfs.tech/t/testground-examples-with-dids-a-nodes-spin-up-profiling/14206/1 "2022-05-12T18:02:44Z")

</div>

Hello, I’m following this repo [here](https://github.com/ipfs/go-ipfs/tree/master/docs/examples/go-ipfs-as-a-library) as a guide for a better approach on IPFS itself. Currently the idea is to use self-infra management for ipfs as own cluster, avoiding k8s for now. However, the documentation doesn’t mention (at least as far as I research) how different are the results between a local/docker/k8s execution. So if there’s some differences on it, I would love to know, specially because we are aiming parcadev and grafana for visualize the results. Plus, besides the ipfs/textile test repo, is there any other source that is trying to spin up nodes on test and access some DID’s?  
Thanks