# Sharing Gems and Ruby Interpreter among application servers

**URL:** <https://www.ruby-forum.com/t/sharing-gems-and-ruby-interpreter-among-application-servers/172894>\
**Category:** Rails\
**Created:** [July 29, 2009, 4:45pm UTC](https://www.ruby-forum.com/t/sharing-gems-and-ruby-interpreter-among-application-servers/172894 "2009-07-29T16:45:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ACTRAiSER](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/3ec8ea/32.png) [@ACTRAiSER](https://www.ruby-forum.com/u/ACTRAiSER)\
**Post date:** [July 29, 2009, 4:45pm UTC](https://www.ruby-forum.com/t/sharing-gems-and-ruby-interpreter-among-application-servers/172894/1 "2009-07-29T16:45:48Z")

</div>

Hi there,

I have several Rails Applications on different servers which all use  
the same gems and the same ruby interpreter version, installed on each  
of the machines. They are all in the same data warehouse, meaning they  
are all connected in one network via Gbit-Connection.

I was wondering if it would make sense to outsource the gems/ruby  
interpreter to another machine within the network, where all  
application servers would have access to via mounting a directory on  
that new server. It would make it much easier to update gems only on  
one machine for all applications then.

Did anyone try that or has a suggestion or experience with shared  
libraries among servers in a network? Maybe its performancewise a  
disaster or there are other arguments against this idea.

Greets  
-act

---

<div class="post-metadata">

**Author:** ![ACTRAiSER](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/3ec8ea/32.png) [@ACTRAiSER](https://www.ruby-forum.com/u/ACTRAiSER)\
**Post date:** [August 3, 2009, 2:57pm UTC](https://www.ruby-forum.com/t/sharing-gems-and-ruby-interpreter-among-application-servers/172894/2 "2009-08-03T14:57:31Z")

</div>

> Did anyone try that or has a suggestion or experience with shared  
> libraries among servers in a network? Maybe its performancewise a  
> disaster or there are other arguments against this idea.

Probably not a problem performance-wise, just kind of pain to configure  
🙂  
I think there is a way to “freeze all gems” to your ruby distro–that  
might be worth it.  
=r