Watch the sql logs on startup and you will find ypur answer. Look at the queruwles, data beingbreturned and ask yourself if it makes sense. You can get it to start faster by deletung all the objects on the server. Last time I looked, the long startup time has less to do with the cache operation and more to do with by je db retrieval operation. It used to retrieve data from the db like field_dispprop x times, where x equals field_dispprop / 1000. Itbwouldbretrieve the entire table to load 1kbrows into cache. Itbwould repeat this until al. Rows were loaded. It would do similarvfor arschema, field, group, etc. Not surebif this still holds true or not today, but the sql logs will confirm. On Feb 19, 2014 6:58 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"
