Desempenho
Posted in 2014
Topics: Logging & Checkpoints
Bom dia Srs.
Hoje efetuei uma verificação com o comando onstat -g ckp e obtive o retorno
abaixo:
Based on the current workload, the physical log might be too small
to accommodate the time it takes to flush the buffer pool during
checkpoint processing. The server might block transactions during checkpoints.
If the server blocks transactions, increase the physical log size to
at least 29804236 KB.
Based on the current workload, the logical log space might be too small
to accommodate the time it takes to flush the buffer pool. The server might
block
transactions during checkpoints. If the server blocks transactions,
increase the size of the logical log space to at least 37956072 KB.
Atualmente meu PLog está assim:
df18d5f8 16 9 0 1250000 1249947 PO-BD /IFMXDATA/ol_logix/plogdbs.000
df18d7e8 17 9 0 5242880 3932157 PO-BD /IFMXDATA/ol_logix/plogdbs2
Pelo que entendi o tamanho do plog está muito pequeno.
Porém o tamanho proposto é muito grande: 29804236 KB.
Alguém poderia me ajudar nisso?
Estou utilizando a versão 11.5
Ignore it. This warning comes out even if a very short term update load
lasting only seconds passed an internal threshold that calculates how much
physical log space you would use if that rate of transactions continued
through an entire checkpoint interval. Just monitor onstat -l near
checkpoints (or the equivalent sysmaster data) to see what percent of your
physical log is filling before a checkpoint and watch onstat -g ckp to see
if you ever get a checkpoint triggered by a PLOG - physical log surpassing
75% full. If no PLOG checkpoints and your physical log isn't close to 75%,
then this is a red herring (ignorable warning).
Art
Art S. Kagel, President and Principal Consultant
ASK Database Management
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on the IIUG, nor any other organization with which I am
associated either explicitly, implicitly, or by inference. Neither do
those opinions reflect those of other individuals affiliated with any
entity with which I am affiliated nor those of the entities themselves.
On Fri, Sep 19, 2014 at 7:03 AM, SANDRO DELAGE <sandrocpd@gmail.com> wrote:
> Bom dia Srs.
>
> Hoje efetuei uma verificação com o comando onstat -g ckp e obtive o retorno
> abaixo:
>
> Based on the current workload, the physical log might be too small
> to accommodate the time it takes to flush the buffer pool during
> checkpoint processing. The server might block transactions during
> checkpoints.
> If the server blocks transactions, increase the physical log size to
> at least 29804236 KB.
> Based on the current workload, the logical log space might be too small
> to accommodate the time it takes to flush the buffer pool. The server might
> block
> transactions during checkpoints. If the server blocks transactions,
> increase the size of the logical log space to at least 37956072 KB.
>
> Atualmente meu PLog está assim:
> df18d5f8 16 9 0 1250000 1249947 PO-BD /IFMXDATA/ol_logix/plogdbs.000
> df18d7e8 17 9 0 5242880 3932157 PO-BD /IFMXDATA/ol_logix/plogdbs2
>
> Pelo que entendi o tamanho do plog está muito pequeno.
> Porém o tamanho proposto é muito grande: 29804236 KB.
> Alguém poderia me ajudar nisso?
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001a11c3783e0f511005036a9d8f
Related threads
- Posting from the Informix-list
- Migrating from IDS 9.40.UC6 to 11.50.UC3
- Ip for a network session
- questions onstat -g