Hardware requirements / guidelines?

RT Users
1

What are the minimum specifications / guidelines for hardware
on which to run RT?

I was unable to find anything specific in the wiki.

2

RT itself doesn’t take all that much. I run mine in a VM with one CPU
core, 2GB RAM, and 8GB disk space. I ran into performance problems when
I was also running MySQL in that same VM. Since I switched to an
external db host, those problems have been completely resolved.

SethOn 11/04/2010 09:15 AM, Jeff Blaine wrote:

What are the minimum specifications / guidelines for hardware
on which to run RT?

I was unable to find anything specific in the wiki.

Seth Galitzer
Systems Coordinator
Computing and Information Sciences
Kansas State University
http://www.cis.ksu.edu/~sgsax
sgsax@ksu.edu
785-532-7790

3

-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-
bounces@lists.bestpractical.com] On Behalf Of Jeff Blaine
Sent: Friday, 5 November 2010 1:16 AM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Hardware requirements / guidelines?

What are the minimum specifications / guidelines for hardware on which to
run RT?

I was unable to find anything specific in the wiki.

It depends heavily upon how many users you intend to have and how many tickets you expect created. If the numbers are small (less than a 40 or so privileged users, only a few hundred tickets a week), a small VM is just fine (as Seth mentioned).

RT its self is just a small web application. The database it uses on the other hand can get large and unwieldy; the database requires considerably more resources than RT.

We have about 30 privileged users, don’t use SelfService bug to through about 1000-1000 tickets a week. We use a Pentium D (older workstation model) server with 4GB of memory for both front end and database. We use MySQL for RT’s database, it is about 1.5GB and has about 40,000 tickets. The machine isn’t pushed hard.

Stuart

4

Thanks for the replies.

So basically, when implementing the DB on the same host
as the web server, the hardware requirements are:

 "The hardware requirements of the DB choice and DB
  size, so reference the DB docs and maybe add 10%."

Fair?

It would be nice to have a record of where people hit trouble
(if they did), what they expanded to (if they did), and overall
what is working for people.

It would seem to me that Best Practical would have this sort
of information available as part of their contract work. I
don’t think, “Just throw a modern dual-core box with 16GB at
it” would be an acceptable answer to a customer asking "What
are the hardware requirements for us with 1000 tickets per
month?"On 11/4/2010 10:50 PM, Stuart Browne wrote:

-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-
bounces@lists.bestpractical.com] On Behalf Of Jeff Blaine
Sent: Friday, 5 November 2010 1:16 AM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Hardware requirements / guidelines?

What are the minimum specifications / guidelines for hardware on which to
run RT?

I was unable to find anything specific in the wiki.

It depends heavily upon how many users you intend to have and how many tickets you expect created. If the numbers are small (less than a 40 or so privileged users, only a few hundred tickets a week), a small VM is just fine (as Seth mentioned).

RT its self is just a small web application. The database it uses on the other hand can get large and unwieldy; the database requires considerably more resources than RT.

We have about 30 privileged users, don’t use SelfService bug to through about 1000-1000 tickets a week. We use a Pentium D (older workstation model) server with 4GB of memory for both front end and database. We use MySQL for RT’s database, it is about 1.5GB and has about 40,000 tickets. The machine isn’t pushed hard.

Stuart