Subject | Re: [IBO] 1:Trusware Repository ?? 2:Slowing down over time |
---|---|
Author | Helen Borrie |
Post date | 2006-01-26T10:30:09Z |
At 08:06 PM 26/01/2006, you wrote:
webapp so that bona fide Trustware subscribers will be able to access
the sources through a community account. This is intended to make it
easier to keep track of Trustware subscribers and reduce the volume
of pirate downloads.
don't explicitly control your IB_Connection.DefaultTransaction using
StartTransaction and Commit, you will get AutoCommit and commit will
be CommitRetaining. Logging out and then back in will cause a final
hard commit or rollback (depending on the state of transactions at
the time) and allow garbage collection to move forward....until it
builds up again and things slow down again.
The situation will be worse with PessimisticLocking active in your
datasets: PessimisticLocking will not be working at all but every
record you visit in Edit mode will have a dummy update committed for
it and increase the window between the OIT and the OAT.
clean, controllable and simple. DefaultTransaction is for bunny-rabbits (IMO!)
Helen
>Question for Jason and Helen:Jason's in the process of adding functionality to the community
>
>What happened to trusware repository? Why it is not updated?
webapp so that bona fide Trustware subscribers will be able to access
the sources through a community account. This is intended to make it
easier to keep track of Trustware subscribers and reduce the volume
of pirate downloads.
>Question for All members:This sounds like the classical problem of CommitRetaining. If you
>
>Application without explicite Transaction (No TIB_Transaction
>component) is slowing down over time. Log out and Log in speeds up
>database access.
don't explicitly control your IB_Connection.DefaultTransaction using
StartTransaction and Commit, you will get AutoCommit and commit will
be CommitRetaining. Logging out and then back in will cause a final
hard commit or rollback (depending on the state of transactions at
the time) and allow garbage collection to move forward....until it
builds up again and things slow down again.
The situation will be worse with PessimisticLocking active in your
datasets: PessimisticLocking will not be working at all but every
record you visit in Edit mode will have a dummy update committed for
it and increase the window between the OIT and the OAT.
>Does anyone have expirience that introducing TIB_Transaction canIt is my belief that instantiating your transactions makes everything
>resolve this problem?
clean, controllable and simple. DefaultTransaction is for bunny-rabbits (IMO!)
Helen
>Rade
>
>
>
>
>
>
>___________________________________________________________________________
>IB Objects - direct, complete, custom connectivity to Firebird or InterBase
> without the need for BDE, ODBC or any other layer.
>___________________________________________________________________________
>http://www.ibobjects.com - your IBO community resource for Tech Info papers,
>keyword-searchable FAQ, community code contributions and more !
>Yahoo! Groups Links
>
>
>
>