Look at the BlobInserts sample application. Your suggestion that you ran out
of memory tells me you were doing this with the wrong component. Use a
TIB_DSQL component with an INSERT statement or make a stored procedure that
loads the data and call EXECUTE PROCEDURE.

HTH,
Jason Wharton
CPS - Mesa AZ
http://www.ibobjects.com

----- Original Message -----
From: "Paul Little" <paul.little@...>
To: <IBObjects@yahoogroups.com>
Sent: Friday, January 26, 2001 5:57 AM
Subject: Re: [IBO] data posting times


> Hi Luc,
>
> No, that's not a typo. The reason I write field for field is rather
> complicated I'm afraid. My app is a financial risk model and the data
> that is being written is things like GDP, CPI, FXrates and so on. There
> are a lot of interdependancies amongst these factors and they have to be
> calculated in a certain order. Each of these data types are calculated
> for a certain number of economic periods (quarters) and for a certain
> muber of economic cycle scenarios (both of these factors are user inputs
> so cannot be know beforehand) and for a number of different currencies.
> There can be up to about 120 periods, up to about 2500 scenarios and
> between 3 and 10 currencies (i.e. a possible 3000000 combinations). I
> tried doing the calculations for a complete record before posting but
> kept running out of memory!
>
> The table I am writing to has a three field primary key (scenario,
> period and currency) and seperate fields for the economic data so that
> for each data type there is a unique scenario/period/currency record.
> e.g.
>
> scn prd ccy data1 data2.......etc
> 1 1 A x y
> 1 2 A x y
> 1 3 A x y
> 1 1 B x y
> 1 2 B x y
>
> etc (you get the idea).
>
> I've tried a few different table configurations but this, I think, gives
> the best usage of disk space as the number of fields is fixed and the
> number of records is determined by the number of scenarios/periods
> required. I did try a table where the periods 1-120 where the fields and
> each record was a scenario and each data type had it's own table but
> this became pretty unwiedly.
>
> Like I said, any suggestions on speeding things up will be great.
>
> Thanks
> Paul
>
> Lucas Franzen wrote:
> >
> > Paul,
> >
> > 10 secs per field? (why do you write field for field?, is this a typo
> > and you meant record???)
> >
> > I do think, you should really speed up, your writing :-)
> >
> > Of course there's no rule, how fast data is written (hardware equipment,
> > record size, etc. all influence this), but you should be able to write
> > any record within the fraction of a second.
> >
> > Or yo you have triggers on that table, that will call a lot of other
> > things that will slow down the write that dramatically????
> >
> > Luc
> >
> > Paul Little schrieb:
> > >
> > > Hi,
> > >
> > > I noticed a couple of threads in the past about the speed (or lack of
> > > it) with IBO. I have just completed the first stage of my app and
tried
> > > it out.
> > >
> > > I was a bit dissapointed by the speed that my data was written to the
> > > database. By rough timing it was about 10 seconds per field. Is this
> > > normal or is there something I could do to speed things up a bit?
> > >
> > > I am using:
> > > IBO3.6
> > > Interbase 5.6
> > > Delphi 5 (proff)
> > >
> > > My c/s app lives on a single machine (i.e. no network) and writes to
the
> > > db are done via sp's which are called within a loop and write one
field
> > > per record on each activation.
> > >
> > > Any hints gratefully received.
> > >
> > > TIA
> > > Paul
>
>
>