This is a notification from the Help Desk. On Jul 02, 2011 @ 02:49 pm, darshak.modi@elitecore.com wrote: Use case mean, any Case study or client ? Best Regards, Darshak Modi +91 9909008245 darshakamodi@gmail.com ==Ticket History== On Jul 02, 2011 @ 02:48 pm, dboyes@sinenomine.net wrote: Thanks for that.I can go for 4 machines 2 for apps and 2 for DB, not an issue at all. Is it anywhere implemented? Any use case? That's pretty much the standard recommendation we use for our deployments. We've done hundreds of the. What do you mean by use case? ------ On Jul 02, 2011 @ 02:48 pm, darshak.modi@elitecore.com wrote: Hey Guys, Thanks for that.I can go for 4 machines 2 for apps and 2 for DB, not an issue at all. Is it anywhere implemented? Any use case? And yes main question was comparison with other systems :) Best Regards, Darshak Modi +91 9909008245 darshakamodi@gmail.com ------ On Jul 02, 2011 @ 02:48 pm, dboyes@sinenomine.net wrote: On 10/16/10 9:01 AM, "Nils Leideck - ITSM" wrote:

All I can say is that 10000 tickets should not be the problem to create, it is just one ticket per 8.5 seconds. You should of consider if the ticket is closed with 4 or 5 actions or if there is a high traffic in terms of customer contacts for a single ticket.

10000 tickets a day is certainly achievable.... But....

1000 Agents, well Š AFIAK we have such systems, but I am not sure if there is one running on a single box - might depend on the definition of ³a single box².

Unless you are planning to acquire mainframe class hardware (and by mainframe, I mean the traditional IBM type), you are unlikely to support 1000 users on one box, and regardless of what software you choose, you would be foolish to try -- too big a possibility of hardware failure taking out what sounds like your primary call center (at least with those ticket volumes). You should plan on at least 4 machines (2 for the ticketing app, 2 for the database) and plan on clustering them for high-availability, using a smart load balancer for the ticketing app so that an agent remains on the same system unless there is a system failure. Now if you do have a mainframe system, let's talk off list. OTRS runs very well there. 8-) -- db --------------------------------------------------------------------- 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 ------ This is an automated response. Your issue has been noted. We'll be in touch soon. Please reply to this email or visit the URL below with any additional details. http://itsupport:1111/portal/view-help-request/651