Rick, Thanks for the input but the reason for going to the 64 bit version was because I kept getting "out of memory" issues and from what I researched the only option was to go to the 64 bit? L.B.
________________________________ From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Rick Cook Sent: Wednesday, July 20, 2011 9:51 AM To: [email protected] Subject: Re: Migration in reverse ** Well, you should start with the 64-bit Java. BMC states that it is 40-45% slower than the 32-bit Java. Rick On Jul 20, 2011 8:22 AM, "Larry Barnes" <[email protected]> wrote: > I have a development server running ITSM 7.6.04 on a VM with 8 gig of > ram and is running SQL 2008 on a separate server. We are dealing with > slowness with ITSM and I'm not sure where the bottle neck is. > > We are running (64 bit) Tomcat and Java; latest releases. > Java has an Initial memory pool of 512 MB and a maximum memory pool of > 2048 MB and the Thread stack size is 4096 KB. > > I may need to move the SQL db off of the 2008 box and place it on a SQL > cluster that is running SQL 2005. Does anyone know of issues with > moving back to 2005 from 2008? > > Thanks for checking, > > Larry B. > > ________________________________________________________________________ _______ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
