Shawn, In later versions of Remedy, you have the options to utilize multiple threads during the startup. As Rick points out, the main thing that Remedy is doing is pulling metadata out of the DB and storing it in RAM. So, there is a direct correlation between how many forms/fields/etc that you have, and how quickly you can get them out of the DB and into memory that determines how quickly your Remedy starts. Do you have that dedicated Fiber channel between your DB and App server that Remedy recommends? :)
On Wed, Feb 19, 2014 at 5:57 AM, Pierson, Shawn < shawn.pier...@energytransfer.com> wrote: > ** > > Since I have nothing better to do (just kidding, I'm swamped) I wanted to > see if anyone on the list had a good explanation for something that has > been an issue across multiple versions of Remedy for years. Specifically, > on Windows, why does it take so long for Remedy to start up, and is there > anything that can be done to make it load faster without sacrificing > performance or functionality? > > > > If someone has found a way to get it to start up in less than 30 seconds, > you should be given a job by BMC. It's been a while since I've worked with > Remedy on Unix but I don't recall it taking as long to start as it does on > Windows. > > > > Thanks, > > > > *Shawn Pierson * > > Remedy Developer | Energy Transfer > > > Private and confidential as detailed > here<http://www.energytransfer.com/mail_disclaimer.aspx>. > If you cannot access hyperlink, please e-mail sender. > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
