• 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: optimization/indexing
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: optimization/indexing


  • Subject: Re: optimization/indexing
  • From: Chuck Hill <email@hidden>
  • Date: Wed, 17 Dec 2008 10:39:03 -0800


On Dec 17, 2008, at 9:25 AM, Jeff Schmitz wrote:

Yes, now that I think of it, there is one of these "crazy" joins that's probably coming into play that joins each of my 7000 rows with 65 rows in a different table, so that table must have about 450,000 rows. Any good optimization approaches for these type of one to "very many" relationships? recursive fetch? I can see this table getting into the many millions of rows real fast.

I'd spend some quality time considering a different design. I doubt it is doing a crazy join. My money would be on Mike's prediction of insane amounts of rapidly scrolling SQL. ERXBatchFetching can be a big help here, properly used.



Chuck



On Tuesday, December 16, 2008, at 11:09PM, "Chuck Hill" <email@hidden > wrote:
Either some crazy joins with other tables or something you are not
aware of is going on.  7K rows is tiny.


Chuck


On Dec 16, 2008, at 9:07 PM, Jeff Schmitz wrote:

hmm, I'm not doing an insert at all, just a read.  Kind of thought
there must be something else too though (with my limited experience)
but figured indexing would be a good thing to do regardless before
digging into debugging the real culprit here.

Jeff

On Dec 16, 2008, at 11:01 PM, Mike Schrag wrote:

More than a minute to insert to a 7000 row table?
Do other operations on the same DB take an appropriate amount of
time?  If not I would start looking at DNS or other connectivity
issues.  I can't fathom a FB DB sucking at that level.
this was my first thought, too ... something else is going on
here.  I suspect if sql debug was turned on, you'd see tons of
faulting going on that you didn't realize and that the insert
itself is not actually the slow thing.

ms

_______________________________________________
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

_______________________________________________ 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


-- Chuck Hill Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects










-- Chuck Hill Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects







_______________________________________________ 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: optimization/indexing
      • From: Jeff Schmitz <email@hidden>
References: 
 >Re: optimization/indexing (From: Jeff Schmitz <email@hidden>)

  • Prev by Date: Re: WebObjects 4.5.1
  • Next by Date: Re: Outer Joins?
  • Previous by thread: Re: WebObjects 4.5.1
  • Next by thread: Re: optimization/indexing
  • Index(es):
    • Date
    • Thread