Identifying and Fixing WebCenter Content Performance Issues
By Ken Walker-Oracle on Mar 28, 2014
I was at the auto-parts store the other day, remembering my teenage days when (due to the financial restraints of a minimum wage job) I had to do most of my own maintenance on my car. I drove a 1968 British MGB and I spent a lot of time under the hood to keep her going. Today, modern cars seem to run forever, but you can still purchase diagnostic readers and tools for it. The idea being, that you can plug this device into your car's computer and look at everything that the computer records. I thought I'd try it out for fun. Did it work? Oh, my heavens... it worked a bit too well for me. Gobs of data came streaming out of my car and I had no idea what to do with it!
I suppose the right mechanic could make sense of it all, and after some poking around through various menus I learned that I was, indeed, able to understand quite a bit more of that data than I thought I would. I learned that one of the fuel injectors in my truck was operating 4% shy of "normal" and I learned a host of other things like, how many miles my tires has on them, what pressure they were inflated to, average temperature of my engine oil at operating temperature, optimum speeds for high gas mileage, etc. All I needed was a bit of time and some help from the manual.
WebCenter Content Server has similar on-board diagnostic tools as well (they're free, too!), and they can also spew forth gobs and gobs of data. If you'd like some "hand holding" while you look under the hood of your Content Server to find any performance problems, it's available to you. Check out the newly published note, How to Analyze Content Server's "requestaudit" Tracing for Performance Issues <Note 1641077.1>
This new note will guide you (with specific instructions and screen shots) through the data to find the spots that need a bit of care and attention to get your Content Server running at peak efficiency!