Eduardo,

<< I have been reading something related with FastMM and multicores. The
last version of FastMM (4.97) has some things related with multicores. Next
week I will update the server with this version. >>

As far as I know, that issue has to do with a garbage-collected memory
environment where memory is being allocated in many threads, and freed in a
single GC thread, which the dbsrvr is definitely not using.  Plus, it's a
performance issue, not a memory consumption/address space issue.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim and Raul

Thanks for clarification.

I don´t know much about memory allocations and their details.

I will keep watching the "day by day" routine of the company and if I found
something I will post here.

Eduardo

Tim and Raul

Only to give you a feed back.

We have replaced the Windows 2008 Server with a 64 bits version and
therefore it can address 8Gb of RAM, the performance change (for better) was
huge and the "problems" with Hard Page decreased a lot but sometimes it
reaches 1200 faults/min. This report is not a problem for me.

When it is reported by users (performance) it is very good to hear.

Eduardo

Eduardo,

<< We have replaced the Windows 2008 Server with a 64 bits version and
therefore it can address 8Gb of RAM, the performance change (for better) was
huge and the "problems" with Hard Page decreased a lot but sometimes it
reaches 1200 faults/min. This report is not a problem for me. >>

Thanks for the feedback.  I suspect that the extra memory gave Windows and
all of the running processes more room to "breathe", resulting in the better
performance.  Even though a 32-bit process can only use an address space of
2GB, it would probably take a 64-bit OS that can use 8GB or more to allow
for most of the 32-bit address space for the DBISAM Database Server process
to reside in physical memory instead of constantly being swapped in and out.

--
Tim Young
Elevate Software
www.elevatesoft.com

On Thu, 18 Nov 2010 16:58:21 -0500, "Tim Young [Elevate Software]"
<timyoung@elevatesoft.com> wrote:

>Eduardo,
>
><< We have replaced the Windows 2008 Server with a 64 bits version and
>therefore it can address 8Gb of RAM, the performance change (for better) was
>huge and the "problems" with Hard Page decreased a lot but sometimes it
>reaches 1200 faults/min. This report is not a problem for me. >>
>
>Thanks for the feedback.  I suspect that the extra memory gave Windows and
>all of the running processes more room to "breathe", resulting in the better
>performance.  Even though a 32-bit process can only use an address space of
>2GB, it would probably take a 64-bit OS that can use 8GB or more to allow
>for most of the 32-bit address space for the DBISAM Database Server process
>to reside in physical memory instead of constantly being swapped in and out.

I seem to have this issue as well. Windows Server 32bit with 4Gb RAM
running KBmmw 2.6, DBISAM 3 and Delphi5. Running the KBmMw server
through Firedaemon as a service and by the end of the day it is
running slow. Restart the KBmMw Firedaemon service and it is off like
lightening again.

Is Windows Server 2008 simply crap at using RAM, or is 4Gb simply not
enough? Haven't narrowed down if it might be Firedaemon yet but
something is making my DBISAM system slower and slower.

Any further pointers would be handy, or simply knowing it isn't
DBISAM, KBmMw, etc would help.

Charles

<<
Is Windows Server 2008 simply crap at using RAM, or is 4Gb simply not
enough? Haven't narrowed down if it might be Firedaemon yet but
something is making my DBISAM system slower and slower.
>>
Unfortunately I really don´t know but when I upgrade my hardware to 8Gb RAM,
*ALL* problems dissapeared and the most important thing: the users noticed
the speed gain and report it to me.

Eduardo

On Thu, 10 Feb 2011 13:49:15 -0300, "Eduardo [HPro]"
<contato@hpro.com.br> wrote:

>Unfortunately I really don´t know but when I upgrade my hardware to 8Gb RAM,
>*ALL* problems dissapeared and the most important thing: the users noticed
>the speed gain and report it to me.
>
>Eduardo
>

Did you have the same issue of it slowing down? In the morning it is
extremely fast but by early evening it has around a six fold decrease
in speed. Re start the DBISAM server (or in my case KBmMw server) and
it is instantly back to lightening fast. Spent hours, of not days, on
this and can't see an issue, though the memory manager in Server 2008
is re-written and many folk have issues, only this thread comes up
with an 'appreciated' solution.

Not sure how big a job changing from a 32bit to a 64bit is on our
system. 32bit and adding another 4Gb of RAM isn't going to work and
will need to 64bit the OS I suppose.

I have a similar, intermittent, effect using ElevateDB in fileserver mode over a mixed Vista/XP network. Reboot the client machine and speed picks up again.


There seems to be no consistency as to the cause, the nature of use, programs running etc.

Roy Lambert

Charles

> Did you have the same issue of it slowing down? In the morning it is
> extremely fast but by early evening it has around a six fold decrease
> in speed. Re start the DBISAM server (or in my case KBmMw server) and
> it is instantly back to lightening fast. Spent hours, of not days, on
> this and can't see an issue, though the memory manager in Server 2008
> is re-written and many folk have issues, only this thread comes up
> with an 'appreciated' solution.

Yes, but these slowdown occurred during the day. Not only in the evening.
It depends on what the users were doing.

And yes, you are right: to use 8Gb RAM you need Windows 2008 64 bits.

Eduardo

This is the KBmMw server that we have to reboot not the clients.

Currently looking at the below options:

MaxTableDataBufferSize
 MaxTableDataBufferCount
 MaxTableIndexBufferSize
 MaxTableBlobBufferSize
 MaxTableBlobBufferCount

Whilst DBISAM doesn't use them in remote use I'm guessing that KBmMw
is using DBISAM in Local mode, thus will be using the above settings.
I think I need to tweak (down) the default settings when using DBISAM
with KBmMw?

Our current thought train is that my KBmMw server is only using 20mb
of RAM and then starts using a lot of page filing. The default
settings of the above might be affecting this, as I don't really want
DBISAM using any buffering when used with KBmMw really?

KBmMw 2.6 and DBISAM 3 used here.