
Copyright © 2001, 2015, Oracle and/or its affiliates. All rights reserved.
Application Server
Logging
Although logging is a vital function in Oracle Transportation Management, excessive logging is very
common cause of poor performance. This is particularly true of bulk planning processes. The Log Files
and Logging Overview pages can be used to review what logs are currently enabled. You can also
temporarily disable all logging by setting the following property:
glog.log.suppressAll=true
Setting this property can be a quick method of determining whether logging is the cause of a
performance issue.
Note: Log File and Logging Overview pages on the Configuration and Administration menu
can only be used to display and configure details about log files enabled on the application
server and web server. Logging on the web server can only be controlled through
glog.properties, the WEB_CUSTOM property set or Log File pages that are of type WEB.
Another way to determine if logging is impacting performance is to look at the rate at which log files
are turning over. On the server running Oracle Transportation Management, you can perform a quick
scan of the directory containing the Oracle Transportation Management logs files. If this reveals a log
file that is turning over a 10MB log file several times per second, it is very likely to be impacting
performance.
LogIds with a suffix of “Debug” or “Details” have the potential to log significant amounts of data and
should be avoided unless directed to be by Support. Ad-hoc logs are the most dangerous because they
generate logging regardless of the user logged in. On the other hand, User logs only write to the log
file when that particular user is logged in and using Oracle Transportation Management. In some
scenarios user logs can still have a significant impact on performance, even if that particular user is
not logged in. This logging happens because there is a certain amount of overhead in generating a log
message. The overhead occurs before Oracle Transportation Management determines, based on the
logged in user, that it does not need to write the message to the log file. For this reason, having many
user logs with detailed logging enabled can have a significant impact on performance.
Oracle Transportation Management Business Object Caches
The Oracle Transportation Management Business Object caches are maintained by Oracle
Transportation Management. The majority of Oracle Transportation Management Business Objects
caches use a Least Recently Used (LRU) strategy to maintain the cache. When an LRU cache reaches
its maximum, a one-for-one exchange is made for the new object and the least recently used object in
the cache. Most static data used by Oracle Transportation Management business logic is maintained in
one of these caches. The App-tier Caches utility page, located on the menu under Technical Support –
Diagnostics and Tools – Caches, can be used to review statistics on these caches.
The size of a Business Object Cache can have a significant impact on performance. The efficiency of a
cache is measured by its hit ratio. A low hit ratio is a possible indication of an undersized cache. If a
cache has reached its capacity and the hit ratio is low (less than 0.80), performance may be impacted.
Increasing the maximum size of this cache may increase system performance. Temporary changes
can be made to the cache using the diagnostic screen, but the changes will revert to the default upon
restart. To permanently change the size of a cache the appropriate glog.property must be set. For
example, the size of the Rate Offering cache is set by the following property:
glog.cache.TRateOfferingCache.capacity=2000
It is important to note that increasing the size of the cache has the adverse affect of increasing
memory usage, so changes should be done incrementally and with thorough testing.
Kommentare zu diesen Handbüchern