Subject | Re: [firebird-support] Slow response on a big database? |
---|---|
Author | Allies Xposs |
Post date | 2009-02-16T18:27:37Z |
thanks @anderson for your Idea... that really good idea..
This thing of frequently "refreshes" of data must be done carefully. Make
sure you have a good WHERE so you don't refresh tousands of records each 10
sec or so.
i must be refresh at 10 = 15 sec if user stand by at PENDING BILL page. because system must be always check input data sales from another computer...
maybe i must try change ibclientdataset.
and re-check my sql statement (Where clause..etc..)
what this slow response if :
1. Load data 30 - 50 record from MYCR table (Have 50.000 record)
2. MYCR have a related 3 another table (1. Master Item table have 2.500 record, 2. data history Open Room 35.000 record and Master Room 500 record)
3. 40 user client at this time
load data need 5 sec to display 30-50 record ?
thanks...
This thing of frequently "refreshes" of data must be done carefully. Make
sure you have a good WHERE so you don't refresh tousands of records each 10
sec or so.
i must be refresh at 10 = 15 sec if user stand by at PENDING BILL page. because system must be always check input data sales from another computer...
maybe i must try change ibclientdataset.
and re-check my sql statement (Where clause..etc..)
what this slow response if :
1. Load data 30 - 50 record from MYCR table (Have 50.000 record)
2. MYCR have a related 3 another table (1. Master Item table have 2.500 record, 2. data history Open Room 35.000 record and Master Room 500 record)
3. 40 user client at this time
load data need 5 sec to display 30-50 record ?
thanks...
--- On Mon, 2/16/09, Anderson Farias <peixedragao@...> wrote:
From: Anderson Farias <peixedragao@...>
Subject: Re: [firebird-support] Slow response on a big database?
To: firebird-support@yahoogroups.com
Date: Monday, February 16, 2009, 12:52 PM
Hi,
> I dont used JOIN SQL statement, but i use related table with
> IBCLIENTDATASET from Delphi.
DON'T. Where you can use SQL JOIN instead of "linking" datasets on client
side
>but i used WHERE and ORDER BY SQL Statment at my IBCLIENTDATASET.
you should no use IBClientDataSet this is a droped component. Use
IBQuery+DataSetProv ider+ClientDataS et.
ClientDataSets can be easilly sorted (and very fast) so.. you can avoid
using ORDER BY that may slow some of your queries down.
The good thing about this ClientDataSet aproach (among other things) is that
if done correctly you won't have problems with long running transactions.
> 5 table always open, and 4 table open/close.
This thing of frequently "refreshes" of data must be done carefully. Make
sure you have a good WHERE so you don't refresh tousands of records each 10
sec or so.
> for next Project Application, must be run/use/handle for 80 client at 18
> floor.
> so confused if my applicati9on can not handled..
If you take care of your queries ("where" clauses, etc) and your transaction
handling than you'll be fine!
Regards,
Anderson Farias
[Non-text portions of this message have been removed]