Re: optimization/indexing
Re: optimization/indexing
- Subject: Re: optimization/indexing
- From: Lists <email@hidden>
- Date: Tue, 16 Dec 2008 21:47:11 -0700
- Organization: Loch Garman
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.
Jeff Schmitz wrote:
Am reading the frontbase docs now. No problem on the CPU load, server
is offline just being readied for production using my snazzy new
EOFized app (which currently takes a minute+ per page request =8*O)
Last question, I'm thinking PERSERVE TIME over PERSERVE SPACE. Disk
space is CHEAP. right?
On Dec 16, 2008, at 10:21 PM, Guido Neitzer wrote:
On 16.12.2008, at 21:10, Jeff Schmitz wrote:
SQL?!? So unclean ;-)
Is adding the index using frontbase manager something that can be
done after a table is populated? Or will I need to export and
re-import my data? Sorry, I'm far from a database expert.
You can add indexes at any time. Just be aware that big tables
(meaning starting with hundreds of thousands of rows) can take a
while to index and that inserting in big tables with many indexes can
be a bit slow (at least on FrontBase 4.x).
cug
_______________________________________________
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