Hi Matthias,

> > what is your record size?
> > what are you saving in rows? divx film, mp3, mp4, jpg blobs?
>
> Not at all :-)
>
> ID Integer Primary Key
> DATETIME Timestamp
> IP Varchar(15)
> PAR1, PAR2, PAR3, PAR4, PAR5 Varchar(80)
> RESULT Integer
> USERID Integer Foreign Key on Users(ID)
> SOURCE Integer
> SSL Integer
>
> That's it.

4+8+17+5*82+4+4+4+4 = 455 bytes, not so big.(confession: calc used)
I hope your page size and disk block size match, like as at last 4KB.
Also, exclude your fdb file type from antivirus programs, system
restore services.

Problem here is Foreign Key i think.
It was a genetic promlem of FB and fixed in FB v2.
if your referance column has thousands dulicates, don't use foreign
key declaration. FB losts itself repeated index nodes with DISK I/O.
Try to create your custom based integrity control system.

>
> > i think you have some problems with your HW or SW systems other

than

> > FB.
> > 100 Mb means, more than 12MB second. even you have 1KB rows, you

can

> > send 10,000 rows per second in the lonely nights, not 100!
>
> Hmmm... I'll try on a local machine (client+server on the same
> machine). Maybe my LAN is just 1 Mbit/s instead of 100 Mbit/s :-)
>
> Matthias
>

May be, if you have Wi-fi components in your LAN,
or your physical layer has some problems. :)

Regards.

Ali