# Speeding up pinning for CI

**URL:** <https://discuss.ipfs.tech/t/speeding-up-pinning-for-ci/13314>\
**Category:** Kubo\
**Created:** [January 29, 2022, 9:31pm UTC](https://discuss.ipfs.tech/t/speeding-up-pinning-for-ci/13314 "2022-01-29T21:31:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![amarao](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/amarao/32/5909_2.png) [@amarao](https://discuss.ipfs.tech/u/amarao)\
**Post date:** [January 29, 2022, 9:31pm UTC](https://discuss.ipfs.tech/t/speeding-up-pinning-for-ci/13314/1 "2022-01-29T21:31:26Z")

</div>

I have CI pipeline which checks my playbooks. They install go-ipfs and pins files we need for operations. Those files are pinned on pinata and on our (non-CI) servers.

The time pinnig works varies drastically. Sometime my workflow ends in 4 minutes, sometimes it’s over 20 minutes of retries.

Is there any way to speedup pinning? What is causing slow pinning?

---

<div class="post-metadata">

**Author:** ![Jorropo](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/jorropo/32/3230_2.png) [@Jorropo](https://discuss.ipfs.tech/u/Jorropo)\
**Post date:** [January 30, 2022, 11:50am UTC](https://discuss.ipfs.tech/t/speeding-up-pinning-for-ci/13314/2 "2022-01-30T11:50:24Z")

</div>

I work on: [GitHub - Jorropo/linux2ipfs: This is a tool to upload files to estuary.tech in a VERY lightweigth maner.](https://github.com/Jorropo/linux2ipfs)  
Which solves this issue.

It is capable to pin files at gigabytes/s, (capped by the speed of your disks, network or remote servers).  
But I suspect it wont be any faster since pinata servers aren’t.

---

<div class="post-metadata">

**Author:** ![amarao](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/amarao/32/5909_2.png) [@amarao](https://discuss.ipfs.tech/u/amarao)\
**Post date:** [January 30, 2022, 3:52pm UTC](https://discuss.ipfs.tech/t/speeding-up-pinning-for-ci/13314/3 "2022-01-30T15:52:32Z")

</div>

It sounds interesting, but I have a rather small amount of data (\< 50MB), and I can’t understand logic of slow pining. Is it something related to the way IPFS works, or I need to debug the issue?

---

<div class="post-metadata">

**Author:** ![Jorropo](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/jorropo/32/3230_2.png) [@Jorropo](https://discuss.ipfs.tech/u/Jorropo)\
**Post date:** [January 30, 2022, 5:17pm UTC](https://discuss.ipfs.tech/t/speeding-up-pinning-for-ci/13314/4 "2022-01-30T17:17:53Z")

</div>

50MB should be almost instant, \<3s, my tool is more for many gigs to Tib level of data.

The most likely issue is that pinata is slow.  
I think you should change to a faster pinning service.

You should also note that current implementation of bitswap are not fast, in the precise case where you upload to a pinning service, it is faster to stream exporting `.car` files (archive of IPLD blocks) and send that over http stream, tls, ssh, …

---

<div class="post-metadata">

**Author:** ![susarlanikhilesh](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/susarlanikhilesh/32/4112_2.png) [@susarlanikhilesh](https://discuss.ipfs.tech/u/susarlanikhilesh)\
**Post date:** [September 19, 2023, 11:55am UTC](https://discuss.ipfs.tech/t/speeding-up-pinning-for-ci/13314/5 "2023-09-19T11:55:53Z")

</div>

I am not using any pinning service, but just using ipfs pin add . For a 2GB file, it takes so much amount of time to get pinned and these both systems are sitting in far regional areas. Is there any way to dig more and look why it is taking time ?