• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Some help with Optimization
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Some help with Optimization


  • Subject: Re: Some help with Optimization
  • From: Kieran Kelleher <email@hidden>
  • Date: Thu, 9 Feb 2006 23:04:36 -0500

A great feature to help you see the WHERE part of suboptimal indices is the built-in EOAdaptorContextDelegate in Project Wonder. Simply include ERExtensions framework and put something like this in your Properties file.....

log4j.logger.er.extensions.ERXAdaptorChannelDelegate.sqlLogging=TRUE

######################################################################## #
# ERXAdaptorChannelDelegate
######################################################################## #
## Enable delegate to emit SQL debugging info. The Logger used is
## log4j.category.er.extensions.ERXAdaptorChannelDelegate.sqlLogging
er.extensions.ERXAdaptorChannelDelegate.enabled=true


## How long a statement must run to cause a log message. Messages with longer than
## error also emit a stack-trace
er.extensions.ERXAdaptorChannelDelegate.trace.milliSeconds.debug=10
er.extensions.ERXAdaptorChannelDelegate.trace.milliSeconds.info=100
er.extensions.ERXAdaptorChannelDelegate.trace.milliSeconds.warn=1000
er.extensions.ERXAdaptorChannelDelegate.trace.milliSeconds.error=5000


## MaxLength of the message
er.extensions.ERXAdaptorChannelDelegate.trace.maxLength = 3000

## What entities to watch
er.extensions.ERXAdaptorChannelDelegate.trace.entityMatchPattern = .*

_________________________________________________

One thing about EOModeler is that every attribute has optimistic locking turned on by default. This creates big WHERE clauses which can slow you down on non-indexed fields. My feeling is that optimistic locking should be turned on on essential fields only and then index those since WO _will_ use then in sql WHERE clauses.

Regards, Kieran

On Feb 9, 2006, at 9:32 PM, Chuck Hill wrote:

I have no idea whether my suggestions will accelerate your app, but they'd be worth a quick try. Also, you should ensure that the DB columns involved are indexed.

Yep. That is probably the #1 cause of slow WO apps.

_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Some help with Optimization
      • From: Chuck Hill <email@hidden>
References: 
 >Some help with Optimization (From: Owen McKerrow <email@hidden>)
 >Re: Some help with Optimization (From: Art Isbell <email@hidden>)
 >Re: Some help with Optimization (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: WO, Java and Microsoft Active Directory
  • Next by Date: Re: Some help with Optimization
  • Previous by thread: Re: Some help with Optimization
  • Next by thread: Re: Some help with Optimization
  • Index(es):
    • Date
    • Thread