
Hello guys, I needing a table, with a number of users or tickets (don't know which is better to estimate) and the hardware needed to the server, something like this: 50 agents - ~1 GB RAM, processor Y and X GB HD 100 agens - ~ 2 GB RAM, processor Z and Y GB HD does anyone have it? Or can help me to build one? Thanks

On 29-08-2011 19:59, Wagner wrote:
I needing a table, with a number of users or tickets (don't know which is better to estimate) and the hardware needed to the server, something like this:
50 agents - ~1 GB RAM, processor Y and X GB HD 100 agens - ~ 2 GB RAM, processor Z and Y GB HD
Windows or Linux? I think the best way to measure this is how many tickets you expect to handle daily. -- Lars

Linux
yes, I was estimating something like in the maximum of 5 tickets per user
per day
Thanks
2011/8/30 Lars Jørgensen
On 29-08-2011 19:59, Wagner wrote:
I needing a table, with a number of users or tickets (don't know which is better to estimate) and the hardware needed to the server, something like this:
50 agents - ~1 GB RAM, processor Y and X GB HD 100 agens - ~ 2 GB RAM, processor Z and Y GB HD
Windows or Linux? I think the best way to measure this is how many tickets you expect to handle daily.
-- Lars ------------------------------**------------------------------**--------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/**pipermail/otrshttp://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/**listinfo/otrshttp://lists.otrs.org/cgi-bin/listinfo/otrs

I can give you some info about our environment:
Some 700-odd users and 10 agents. This is a realy low traffic system
with ~1900 Tickets in 8 Months, so about 11 Tickets per working day.
This runs on a FreeBSD system with a 4 core Intel XEON E5620 @2,4 Ghz
and 8 GB of RAM.
This is probably way oversized as we are currently using about 2.5GB
of RAM and the most demanding CPU job would be the backup at night and
all those icinga checks...
Cheers
Phil
--
It might be just possible, by lying very still in a cellar somewhere,
to get through a day without committing a crime. But only just. And,
even then, you were probably guilty of loitering.
- Terry Pratchett: Feet of clay.
GPG KEY ID (Philipp Bieber): 0x0185E301
FINGERPRINT: CA81 28C2 E63F DAF8 5ED4 DACB 7C26 EE5B 0185 E301
Philipp Bieber - philbieber@gmail.com
2011/8/30 Wagner
Linux
yes, I was estimating something like in the maximum of 5 tickets per user per day
Thanks
2011/8/30 Lars Jørgensen
On 29-08-2011 19:59, Wagner wrote:
I needing a table, with a number of users or tickets (don't know which is better to estimate) and the hardware needed to the server, something like this:
50 agents - ~1 GB RAM, processor Y and X GB HD 100 agens - ~ 2 GB RAM, processor Z and Y GB HD
Windows or Linux? I think the best way to measure this is how many tickets you expect to handle daily.
-- Lars --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

On 30-08-2011 14:16, Wagner wrote:
Linux
yes, I was estimating something like in the maximum of 5 tickets per user per day
And how many users and agents? If there's not an abnormal bunch of users (less than 2-300 tickets a day), you can run this on a pretty low-powered system. If you make sure MySQL is tuned for performance and that you use mod_perl for OTRS (both setups described in the installation guide), a dual core machine with 4 GB ram should be able to handle it without issue. Currently we use a single core machine with 2 GB ram to handle about 30 new tickets every day, supporting about 30 agents and 500+ users. The system contains more than 5,000 tickets. There is nothing slow in that setup. -- Lars

How can I estimate the number of tickets per user per day?
2011/8/30 Lars Jørgensen
On 30-08-2011 14:16, Wagner wrote:
Linux
yes, I was estimating something like in the maximum of 5 tickets per user per day
And how many users and agents?
If there's not an abnormal bunch of users (less than 2-300 tickets a day), you can run this on a pretty low-powered system. If you make sure MySQL is tuned for performance and that you use mod_perl for OTRS (both setups described in the installation guide), a dual core machine with 4 GB ram should be able to handle it without issue.
Currently we use a single core machine with 2 GB ram to handle about 30 new tickets every day, supporting about 30 agents and 500+ users. The system contains more than 5,000 tickets. There is nothing slow in that setup.
-- Lars ------------------------------**------------------------------**--------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/**pipermail/otrshttp://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/**listinfo/otrshttp://lists.otrs.org/cgi-bin/listinfo/otrs

Hi,
On Tue, Aug 30, 2011 at 15:13, Wagner
How can I estimate the number of tickets per user per day?
there's only one answer to that: trending. There's no way we can guess that for you, it depends on so many factors. The same as for the OTRS hardware sizing; it's very difficult to do. Even if you have the # of tickets you expect, it depends on lots of factors; for instance the average ticket size and the # of articles per ticket. In my experience platform choice (linux or windows) is not that much of an issue with sizing, a 4core server with 8GB memory will be able to generally the same load wether it runs Windows or Linux. At least the difference is not very significant. In general it's always very nice to have so much RAM to be able to hold the database in memory. Also, virtualizing a database server means a 30-40% performance penalty. (source: Brian Aker) Typically many companies still want to deploy on virtualized servers only; nowadays. But if I had the choice I would prefer a bare metal database server, because of this reason. With the number of agents and tickets you're talking about: 1900 or 5000 tickets or the like on the complete system, you really don't have anything to worry about; then you can also use a virtual machine , assign 4 GB to it and one or maybe two cores, and run the database on the same box as the web server. -- Mike

On 30-08-2011 16:06, Michiel Beijen wrote:
With the number of agents and tickets you're talking about: 1900 or 5000 tickets or the like on the complete system, you really don't have anything to worry about; then you can also use a virtual machine , assign 4 GB to it and one or maybe two cores, and run the database on the same box as the web server.
I can confirm this, above configuration works perfectly for a small system. -- Lars
participants (4)
-
Lars Jørgensen
-
Michiel Beijen
-
Phil Bieber
-
Wagner