# Performance of \`Pkg.status()\` when package directory is NFS mounted

**URL:** <https://discourse.julialang.org/t/performance-of-pkg-status-when-package-directory-is-nfs-mounted/1496>\
**Category:** General Usage\
**Created:** [January 15, 2017, 1:52pm UTC](https://discourse.julialang.org/t/performance-of-pkg-status-when-package-directory-is-nfs-mounted/1496 "2017-01-15T13:52:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![josefsachs](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@josefsachs](https://discourse.julialang.org/u/josefsachs)\
**Post date:** [January 15, 2017, 1:52pm UTC](https://discourse.julialang.org/t/performance-of-pkg-status-when-package-directory-is-nfs-mounted/1496/1 "2017-01-15T13:52:07Z")

</div>

When my Julia package directory is on a local filesystem, `Pkg.status()` takes 2 seconds,  
but when it is located on an NFS mounted filesystem `Pkg.status()` takes over 170 seconds.  
Is this just a fact of life, or is there something that can be done to make the elapsed time  
more reasonable, either in terms of configuration of my system or a potential code change  
in Julia?

---

<div class="post-metadata">

**Author:** ![lobingera](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lobingera/32/211_2.png) [@lobingera](https://discourse.julialang.org/u/lobingera)\
**Post date:** [January 15, 2017, 5:03pm UTC](https://discourse.julialang.org/t/performance-of-pkg-status-when-package-directory-is-nfs-mounted/1496/2 "2017-01-15T17:03:40Z")

</div>

afaiu some time is spend in reading METADATA which is a git repository of a long list of small files and actually a database. This long access (i have 20s on a local filesystem) was one of the drivers of Pkg3.