Dear Helen

Thanks for your time

Here the gstat:

D:\Database>gstat -h msup.fdb

Database "msup.fdb"
Database header page information:
Flags 0
Checksum 12345
Generation 21260075
Page size 4096
ODS version 11.0
Oldest transaction 21260066
Oldest active 21260067
Oldest snapshot 21260067
Next transaction 21260069
Bumped transaction 1
Sequence number 0
Next attachment ID 0
Implementation ID 16
Shadow count 0
Page buffers 0
Next header page 0
Database dialect 1
Creation date Feb 13, 2008 20:13:13
Attributes force write

Variable header data:
Sweep interval: 20000
*END*

The app is written in Delphi.

Again: When i start a query from the client, i see a lot of "Writes
to database". I expect to see "Reads from database". For me not to
explain.

Shall i install the ClassicServer for Tests on the MultiProcessor
Server or is this a bad idee?

Greetings from Switzerland

Haija




--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@...>
wrote:

>
> At 10:13 PM 16/06/2008, you wrote:
> >Thank you Helen.
> >
> >Here some facts:
> >
> >The application work in the local lan only. Our network is tcp/ip
> >based and all components are from cisco. As far as i know the

network

> >works correctly.
> >The application has a front end at the clients with a notif

service

> >attached. Means, that data are stored at clients and all 30 sec

the

> >data are written to the server.
> >At the server i have run a tool named "MiTeC Interbase Query".

There

> >is a Performance Monitor in there and i have run it.
> >When i start a querry to the Database over the app i see at the
> >Performance Monitor a lot of "Writes to database" but not
> >many "Reads from database".
>
> This isn't very clear. First you say that you're using the

database mostly for writes from the clients and then you say you are
seeing writes to database when you run your query tool. You don't
get writes from selects. You don't get reads from inserts. Does the
Mitec tool create some kind of temporary structures?

>
> >Is there a way to post you a printscreen?
>
> Don't want one, thanks. It wouldn't tell us anything useful.
>
> >At the same test i have checked the CPU consumation. Nearly

nothing

> >to do for the cpu. Also the ram consumation is only 650MB incl. OS.
> >The Databasefile has only 150MB.
> >For a Multiprocessor machine is it not better to run classig

server?

> >Classic Server support SMP while Superserver doesn't.
> >The implementator has no idea where the bottleneck is located.
> >
> >Database: Firebird 2.0.3 Superserver
> >DatabaseInterface: I see on the client a firebird client
>
> That is not what is meant by "data access interface". Applications

access the database through an API. A data access interface is a
component of your application programming environment that provides a
language-specific interface between your program and this API.
Examples are VCL, IBX, IB Objects, FIBPlus for Delphi, Jaybird for
Java, the Firebird .NET Provider, ODBC (amongst many others). Poor
performance is almost always the result of faulty techniques in
client programs.

>
> >Users: 60
> >Clients: 2000 and XP
> >
> >Don't know whether the databases were created
>
> A legacy database might have a page size that is too small or an on-

disk structure (ODS) that is too old to take advantage of performance
enhancements in Firebird 2.

>
> You can use the command-line tool gstat to discover these things

and a lot about why your databases might be performing badly. You
could start by running (from the bin directory on the server)

> gstat -h d:\path\to\your\database. Highlight the output by

dragging the mouse and press Enter. That will copy the highlighted
text to the clipboard. Paste the output to the list.

>
> Helen
>