Francesco Lamonica skriver:

> Hi all, it's been a while since i last used FB (not that i used
> anything else :) but i have not been involved with DBs :))
> Now we're planning a project with hundreds of clients (think 5-600)
> that will do insert queries every minute or so (to save status data)
> over WAN and one or two clients that will do select queries to plot
> this information, think of: select avg(myval) from table1 where
> "timestamp<15min ago"
> Since the stored data will grow quite fast (we need to store a few
> months worth of data) have you any recommendation on which kind of
> architecture (both HW and FB) would be suitable?

With 600 inserts every minute and a few months of data (100 days?) you
will end up with about 86 million records.

A simple index on the timestamp would probably do fine without any
special hardware. A large page size would probably be good to reduce
index depth.

I'd recommend turning forced writes off and protect against corruption
by other means, e.g. RAID and UPS. We had a HUGE performance boost when
we switched forced writes off.

I understand that the FB protocol doesn't perform well over a WAN, so
perhaps consider writing a server app that communicates with your
clients in a more efficient way, and have the server app do the actual
FB stuff.

Kjell
--
------------------------------
Kjell Rilbe
DataDIA AB
E-post: kjell.rilbe@...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64


[Non-text portions of this message have been removed]