# Pprof results from go-zenon

**URL:** https://forum.hypercore.one/t/pprof-results-from-go-zenon/127
**Category:** Development
**Created:** [June 16, 2023, 6:34pm UTC](https://forum.hypercore.one/t/pprof-results-from-go-zenon/127 "2023-06-16T18:34:46Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![sol](https://forum.hypercore.one/user_avatar/forum.hypercore.one/sol/32/28_2.png) [@sol](https://forum.hypercore.one/u/sol)
#### Post date: [July 4, 2023, 4:05am UTC](https://forum.hypercore.one/t/pprof-results-from-go-zenon/127/6 "2023-07-04T04:05:52Z")

</div>

> [@Chadass](#):
>
> Where do you guys think it comes from?

I don’t want to jinx it, but I may have resolved the issue.  
Currently soaking the fix on Linux and Windows to see if memory allocation creeps up over time.

Early numbers indicating sub-200 MB memory required for a full node after it has synced, which is very different from the 5GB my _testnet_ node was consuming.  
While syncing with the fix, it fluctuates between 500-1500MB.

I might have discovered a second “leak”; not sure how to characterize it yet, but I may work on another optimization as well.

I’ll confirm my findings with the Golang devs then write a post with troubleshooting steps in case anyone needs to do some performance profiling in the future.

---

_[View the full topic](https://forum.hypercore.one/t/pprof-results-from-go-zenon/127)._