The only issue I have run into are processes crashing. The libumem allocator does some special guarding against illegal memory operations; which, when they occur, cause the offending process to terminate. It's good for bmc because they can find errors in their code, but bad because it impacts reliability. The plugins bundled with ITSM 7 were particularly offensive during the early patch releases. I can't speak as to whether they have gotten any better.
Axton Grams On Mon, Nov 24, 2008 at 6:08 PM, Terry Bootsma <[EMAIL PROTECTED]> wrote: > Hello arslist: > > We have been utilizing ARS 7.1 Patch 004 with ITSM 7.0.2 (latest patch for > Incident, Change, Config, and Problem) on a multi-CPU, high end Solaris box > running DB2. We have had SIGNIFICANT performance issues under high load > running this configuration as a result of our load testing exercise. > > However, after meeting with Remedy engineers yesterday, they suggested that > we replace the standard Solaris memory manager with a preloaded "libumem" > memory manager. This has produced astonishing results and has resolved our > issue of performance under high load with the fact that libumem uses a > different memory allocation model that is more condusive to multi-cpu, > multi-threaded applications. > > My question to the list is this. Have any of you replaced your memory > manager in production with "libumem" and , if so, were there any side > affects of doing so? > > Thanks for any feedback.... Terry > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
