From: Pablo P. <pab...@ju...> - 2010-10-19 12:11:17
|
Hi, my boss want to know some aspects of Mantis, I foward the email he sends me, if anyone can help with it, it would be highly appreciated. /Hi I'm working for a regional government organization at Spain and we decided Mantis to be our service desk software due to prices and licences policies, lack of functionalities, development kit & environment and overall costs in a customized application created about eight years ago on a basic BMC Remedy ARS engine, still in production. The figures are about 90.000 incidents per year, 100 actual manager users and 10.000 intended reporter users who still use the phone to open the incident on the service desk and we have to get them moved to a web interface because this service is external (outsourcing) and works on a per-call basis costs. The plan is a pilot stage building one medium-sized service line on Mantis (as a project) and collecting data in order to to design and plan full migration. For that, we're looking for references on scalability and performance specific to Mantis (beyond MySQL & HTTP Server related) if any. Specifically, I'd like to share experiences on programming plugins using PHP functions oci_* because the plugins we've implemented to integrate Mantis with the pre-existing corporate Oracle databases send calls to these functions. Advice on this later term would be highly appreciated. Regards / -- Emilio J. Cabezas Dpto. Sistemas de Información (Justicia - Córdoba) Consejería de Gobernación y Justicia Junta de Andalucía Teléfonos: 501446 (957-001446) 501447 (957-001447) 744470 (670-944470) -- |
From: John R. <jr...@le...> - 2010-10-19 13:47:19
|
On 10/19/2010 08:11 AM, Pablo Pedrosa wrote: > The figures are about 90.000 incidents per year, 100 actual manager > users and 10.000 intended reporter users who still use the phone to open > the incident on the service desk and we have to get them moved to a web > interface because this service is external (outsourcing) and works on a > per-call basis costs. That works out to about ~350 issues a day, which doesn't seem like too high of a load assuming it's evenly distributed throughout a workday. The real load would probably be from the 100 users who are looking at and managing those issues, and would also completely depend on how complex your workflow is, and how long the average time that a ticket would go before being closed. > The plan is a pilot stage building one medium-sized service line on > Mantis (as a project) and collecting data in order to to design and plan > full migration. For that, we're looking for references on scalability > and performance specific to Mantis (beyond MySQL & HTTP Server related) > if any. Given the load from above, I should imagine that a single dedicated server should suffice for keeping this running. Using something like the APC module for PHP goes a long way to keeping the load down from PHP when running MantisBT, as it will cache compiled versions of the codebase, rather than needing to read files from the disk at every page load. As a second step for scaling up, the simplest solution would be to separate the database onto a second dedicated server, and utilize heavy in-memory caching for queries to reduce disk load. > Specifically, I'd like to share experiences on programming plugins using > PHP functions oci_* because the plugins we've implemented to integrate > Mantis with the pre-existing corporate Oracle databases send calls to > these functions. Advice on this later term would be highly appreciated. I assume you're talking about having plugins access 3rd party Oracle databases, rather than running MantisBT from Oracle. If I'm correct, it should be perfectly fine to do this in a plugin, assuming that you have proper error handling for database exceptions. I personally don't have any experience with Oracle databases though, so I have no idea how robust the oci_* interfaces are in PHP. Cheers -- John Reese LeetCode.net |