Re: Long Fetch times
Re: Long Fetch times
- Subject: Re: Long Fetch times
- From: Jeff Schmitz <email@hidden>
- Date: Sat, 13 Mar 2010 22:58:38 -0600
The one thing that is different about the data added is they have
similar names (e.g. pool names, entry names), so your comment about
not using LIKE might be a part of it since I assume finding the right
name is harder when there's a lot of similar ones.
On Mar 13, 2010, at 10:53 PM, Chuck Hill wrote:
Let's keep this on the list.
On Mar 13, 2010, at 8:46 PM, Jeff Schmitz wrote:
On Mar 13, 2010, at 10:41 PM, Chuck Hill wrote:
On Mar 13, 2010, at 4:44 PM, Jeff Schmitz wrote:
While running some stress tests I seem to be able to get my
database
(Frontbase) in a state where fetch times take an inordinate amount
of time (e.g. fetches that return no rows take a minute),
Has your stress testing added any data to the database? It sounds
like you have exposed a lack of indexes to optimize your queries, or
have queries that don't optimize well.
some, but not all that much. Much less than I've processed fine in
the past.
Has it added different data? More rows to some tables than is
normal. It just takes a few rows to go from "fine" to "disaster".
and once in that state, even a reboot of the machine won't fix the
problem.
Are the apps and the database on the same machine? Is there any
load
on the machine? Are the stress tests still running?
Yes, everything is simple. Single app, all on the same machine.
Same result on 3 different machines.
Is there anyway to recover such a database?
If you have actually damaged the database (which I doubt), no.
I'd do
a flat file export and re-import it into a new database to see.
I'll be perusing the Frontbase for any ideas, but from experience,
is such behavior symptomatic of any particular problem? I've been
running several years and haven't until now seen such behavior.
It just sounds like you have added enough data that your queries are
no longer sufficiently performant.
I'm guessing (hoping) it's an indexing issue.
That is my assumption so far. I'd try "optimize database" and do a
flat file export and import. If that fixes it, you might just have
index fragmentation.
Chuck
--
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