Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notes on choosing/optimising JRuby #32

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Notes on choosing/optimising JRuby #32

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions views/docs/best-practices/sysadmin.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,18 @@ There are two ways to start an Adhearsion process:

* In the background as a daemon. This is typical for deployment scenarios. To start in this mode call ahn with the "daemon" argument: `ahn daemon /path/to/my/application`

## Choice of Ruby VM

While Adhearsion will run well on CRuby (MRI/YARV) 1.9.3 and above, we generally recommend the use of JRuby for high volume deployments.

### JRuby

On JRuby, several options can be helpful for the smooth running of an Adhearsion application. On one project we have had success with the following options:

```
JRUBY_OPTS="-J-Xmx2048m -J-Xms2048m -J-Xmn512m -J-XX:+CMSClassUnloadingEnabled -J-XX:+UseConcMarkSweepGC -J-XX:MaxPermSize=512M --server"
```

<a href="#" rel="docs-nav-active" style="display:none;">docs-nav-best-practices</a>

<div class='docs-progress-nav'>
Expand Down