# Debugging slow content discovery

**URL:** <https://discuss.ipfs.tech/t/debugging-slow-content-discovery/5440>\
**Category:** Help\
**Created:** [January 9, 2019, 11:34pm UTC](https://discuss.ipfs.tech/t/debugging-slow-content-discovery/5440 "2019-01-09T23:34:40Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![sebaseba](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/sebaseba/32/1615_2.png) [@sebaseba](https://discuss.ipfs.tech/u/sebaseba)\
**Post date:** [January 11, 2019, 9:16am UTC](https://discuss.ipfs.tech/t/debugging-slow-content-discovery/5440/16 "2019-01-11T09:16:45Z")

</div>

RAM wasn’t really an issue.  
Let’s see,  
Node A is a Raspberry Pi 1B with an exterior HDD  
Node B is a Lenovo T410, with upgraded RAM to 6 GB.  
Node C is good/new.

I’m thinking of [trying to make a super basic client](https://discuss.ipfs.tech/t/ipfs-ping-protocol/4658) to better understand how IPFS works and why it needs this many resources/why it’s slow.

---

_[View the full topic](https://discuss.ipfs.tech/t/debugging-slow-content-discovery/5440)._