Subject | Re: Server |
---|---|
Author | Michael Vilhelmsen |
Post date | 2012-06-07T11:25:52Z |
Ah - you are right :)
Its the amount of start/commit I was referring to. My bad.
Statistics are as of now:
Database "E:\DB\OCCeasyPos.Fdb"
Database header page information:
Flags 0
Checksum 12345
Generation 55467812
Page size 4096
ODS version 11.1
Oldest transaction 54691256
Oldest active 55360946
Oldest snapshot 55360946
Next transaction 55467714
Bumped transaction 1
Sequence number 0
Next attachment ID 2040416
Implementation ID 16
Shadow count 0
Page buffers 0
Next header page 0
Database dialect 1
Creation date Dec 24, 2011 20:45:12
Attributes force write
Variable header data:
Sweep interval: 0
*END*
As I said earlier whatever they do, they have on job that makes this go from some 80 (which I find a lot still) to 1700+. And its is 24/7.
The system should is supossed to look for some stock changes, and then make som entrys to fill up items in the store.
This customer has some 40 shops.
And sinse these shops on average have a sale every second minute, this routine (whatever it does) does it i my opinion way to much.
The above statistics might have an very old Oldest transaction due to the server dying this morning.
Ususally there is not that big a gap between transactions.
Its the amount of start/commit I was referring to. My bad.
Statistics are as of now:
Database "E:\DB\OCCeasyPos.Fdb"
Database header page information:
Flags 0
Checksum 12345
Generation 55467812
Page size 4096
ODS version 11.1
Oldest transaction 54691256
Oldest active 55360946
Oldest snapshot 55360946
Next transaction 55467714
Bumped transaction 1
Sequence number 0
Next attachment ID 2040416
Implementation ID 16
Shadow count 0
Page buffers 0
Next header page 0
Database dialect 1
Creation date Dec 24, 2011 20:45:12
Attributes force write
Variable header data:
Sweep interval: 0
*END*
As I said earlier whatever they do, they have on job that makes this go from some 80 (which I find a lot still) to 1700+. And its is 24/7.
The system should is supossed to look for some stock changes, and then make som entrys to fill up items in the store.
This customer has some 40 shops.
And sinse these shops on average have a sale every second minute, this routine (whatever it does) does it i my opinion way to much.
The above statistics might have an very old Oldest transaction due to the server dying this morning.
Ususally there is not that big a gap between transactions.
--- In firebird-support@yahoogroups.com, Svein Erling Tysvær <svein.erling.tysvaer@...> wrote:
>
> >WEBESCON Commit Trans 6/6/2012 2499515 1735.774
> >WEBESCON Login 6/6/2012 859 0.59
> >WEBESCON Logout 6/6/2012 858 0.595
> >WEBESCON Start Trans 6/6/2012 2499516 1735.775
> >WEBESCON Commit Trans 6/7/2012 657036 456.275
> >WEBESCON Login 6/7/2012 232 0.161
> >WEBESCON Logout 6/7/2012 231 0.160
> >WEBESCON Start Trans 6/7/2012 657035 456.274
> >
> >These are the number of connect(Login), disconnect(Logout) and transactions.
> >As you can see they are connecting/disconnection some 1700+ times each minute
> >during the entire day. In my eyes its an total overkill.
>
> 1700 connect/disconnect does sound like a lot (and some kind of connection pooling would be advantageous), but I cannot see that from the numbers you report. What I see is 1700 commits per minute, there seems to be almost two minutes between each connect/disconnect.
>
> What are these 1700 transactions actually doing? Do you have some Firebird statistics like oldest transaction/next transaction etc.?
>
> Set
>