On Thu, Nov 27, 2008 at 8:55 PM, Jeroen T. Vermeulen <email address hidden> wrote:
> I think two sentences got conflated there. I believe these timeouts
> mean that the server is now fetching things from disk again that in the
> past months were constantly cached in memory.
>
> There are optimizations that we discarded to avoid complicating our
> schema optimization a year ago. We could reinstate some of those if the
> problem becomes serious before message sharing is completed.
We still have enough RAM to cache all the ondisk files. It is a
different issue. I only have vague guesses at the moment on what could
cause the perceived behavior. Possibly the global shared area is too
large. Possibly we need more frequent checkpoints.
On Thu, Nov 27, 2008 at 8:55 PM, Jeroen T. Vermeulen <email address hidden> wrote:
> I think two sentences got conflated there. I believe these timeouts
> mean that the server is now fetching things from disk again that in the
> past months were constantly cached in memory.
>
> There are optimizations that we discarded to avoid complicating our
> schema optimization a year ago. We could reinstate some of those if the
> problem becomes serious before message sharing is completed.
We still have enough RAM to cache all the ondisk files. It is a
different issue. I only have vague guesses at the moment on what could
cause the perceived behavior. Possibly the global shared area is too
large. Possibly we need more frequent checkpoints.