Subject | Re: [firebird-support] Firebird in automation |
---|---|
Author | Adomas Urbanavicius |
Post date | 2004-12-01T14:06:39Z |
Michele Cannella wrote:
50 records for each. (or any other desired number)
If it is not 24hrs work and you dont like many threads :))), it should
be ok to make 2 theads : one to write to local que, other to deploy data
from que to database.(FIFO)
When system stops filling data to que, "reader" thread will empty
que.(for example during the night) If it is 24h work, then this que
would become bigger an bigger.... :), never see the end.
Adomas
>If it is 24hrs work, then make 20 threads for example to do inserts of
>Hi all
>
>I am trying to use firebird in an automation environment. A set of
>measures taken from the field must be continuously written to the db.
>Each second aroung 1000 measures must be added to a table like
>that:
> signal_id (integer)
> hour (datetime)
> value (double)
> quality (integer)
>
>I am using C++ in a Windows NT/2000 environment (Visual C++,
>wxWindows, ibpp library). And the idea is to keep around 300000 values
>for each signal
>
>There are performance problems: it seems that the system cannot add so
>many record each second (but 1000 are too much ?)
>
>Someone could suggest some 'trick' to keep using firebird for this job ?
>
>
>thanks
>
>Michele
>
>
50 records for each. (or any other desired number)
If it is not 24hrs work and you dont like many threads :))), it should
be ok to make 2 theads : one to write to local que, other to deploy data
from que to database.(FIFO)
When system stops filling data to que, "reader" thread will empty
que.(for example during the night) If it is 24h work, then this que
would become bigger an bigger.... :), never see the end.
Adomas