Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Memory question

5 posts in NT Last posting was on 2012-05-23 06:32:55.0Z
Alex Schaft Posted on 2012-05-21 08:06:12.0Z
Date: Mon, 21 May 2012 10:06:12 +0200
From: Alex Schaft <alexs@quicksoftware.co.za>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.4) Gecko/20120421 Thunderbird/10.0.4
MIME-Version: 1.0
Newsgroups: Advantage.NT
Subject: Memory question
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 41.21.164.84
Message-ID: <4fb9f71c@solutions.advantagedatabase.com>
X-Trace: 21 May 2012 01:04:44 -0700, 41.21.164.84
Lines: 13
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.NT:1862
Article PK: 1130984

Hi,

We've just commissioned a new server at a client, 64bit with 24gig of
Ram. Ads is 64bit as well, currently running around 170 users for about
37 hours.

Memory (private working set) use according to task manager is around
480mb. My main worry is page faults which is creeping up from over a
million.

Is this something to worry about?

Alex


Mark Wilkins Posted on 2012-05-21 15:55:40.0Z
From: "Mark Wilkins" <a@b.c>
Newsgroups: Advantage.NT
References: <4fb9f71c@solutions.advantagedatabase.com>
In-Reply-To: <4fb9f71c@solutions.advantagedatabase.com>
Subject: Re: Memory question
Date: Mon, 21 May 2012 09:55:40 -0600
Lines: 2
Organization: Sybase
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Newsreader: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
NNTP-Posting-Host: 10.6.193.219
Message-ID: <4fba6521$1@solutions.advantagedatabase.com>
X-Trace: 21 May 2012 08:54:09 -0700, 10.6.193.219
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.NT:1863
Article PK: 1130988

Hi Alex,

A million page faults in 37 hours does not seem excessive to me.

Do you have the MAX_CACHE_MEMORY setting in the Advantage configuration? In
general, I think that on a 64-bit system (with 64-bit ADS), you should
probably not have that setting specified. It is really only useful in a
32-bit system to control the memory usage. On a 64-bit system, I believe it
would only artificially limit the amount of memory that Advantage would end
up using.

Mark Wilkins
Advantage R&D

"Alex Schaft" <alexs@quicksoftware.co.za> wrote in message
news:4fb9f71c@solutions.advantagedatabase.com...
> Hi,
>
> We've just commissioned a new server at a client, 64bit with 24gig of Ram.
> Ads is 64bit as well, currently running around 170 users for about 37
> hours.
>
> Memory (private working set) use according to task manager is around
> 480mb. My main worry is page faults which is creeping up from over a
> million.
>
> Is this something to worry about?
>
> Alex


Alex Schaft Posted on 2012-05-22 07:53:28.0Z
Date: Tue, 22 May 2012 09:53:28 +0200
From: Alex Schaft <alexs@quicksoftware.co.za>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.4) Gecko/20120421 Thunderbird/10.0.4
MIME-Version: 1.0
Newsgroups: Advantage.NT
Subject: Re: Memory question
References: <4fb9f71c@solutions.advantagedatabase.com> <4fba6521$1@solutions.advantagedatabase.com>
In-Reply-To: <4fba6521$1@solutions.advantagedatabase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 196.36.8.34
Message-ID: <4fbb459b@solutions.advantagedatabase.com>
X-Trace: 22 May 2012 00:51:55 -0700, 196.36.8.34
Lines: 45
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.NT:1864
Article PK: 1130987

MAX_CACHE_MEMORY is not set in the registry. I found an article about
LargeSystemCache at
http://technet.microsoft.com/en-us/library/cc784562%28v=ws.10%29.aspx

Seeing that server is only running Ads (along with file sharing for exe
files and dll's), I've now switched that off, and will monitor

I would think that on a big database it would be preferable to have
minimal page faults and more data stored in ram than having it swapped out?

On 2012/05/21 17:55, Mark Wilkins wrote:
> Hi Alex,
>
> A million page faults in 37 hours does not seem excessive to me.
>
> Do you have the MAX_CACHE_MEMORY setting in the Advantage configuration?
> In general, I think that on a 64-bit system (with 64-bit ADS), you
> should probably not have that setting specified. It is really only
> useful in a 32-bit system to control the memory usage. On a 64-bit
> system, I believe it would only artificially limit the amount of memory
> that Advantage would end up using.
>
> Mark Wilkins
> Advantage R&D
>
>
> "Alex Schaft" <alexs@quicksoftware.co.za> wrote in message
> news:4fb9f71c@solutions.advantagedatabase.com...
>> Hi,
>>
>> We've just commissioned a new server at a client, 64bit with 24gig of
>> Ram. Ads is 64bit as well, currently running around 170 users for
>> about 37 hours.
>>
>> Memory (private working set) use according to task manager is around
>> 480mb. My main worry is page faults which is creeping up from over a
>> million.
>>
>> Is this something to worry about?
>>
>> Alex
>


Mark Wilkins Posted on 2012-05-22 18:22:52.0Z
From: "Mark Wilkins" <a@b.c>
Newsgroups: Advantage.NT
References: <4fb9f71c@solutions.advantagedatabase.com> <4fba6521$1@solutions.advantagedatabase.com> <4fbb459b@solutions.advantagedatabase.com>
In-Reply-To: <4fbb459b@solutions.advantagedatabase.com>
Subject: Re: Memory question
Date: Tue, 22 May 2012 12:22:52 -0600
Lines: 1
Organization: Sybase
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Newsreader: Microsoft Windows Live Mail 14.0.8089.726
X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8089.726
NNTP-Posting-Host: 10.6.193.219
Message-ID: <4fbbd91e$1@solutions.advantagedatabase.com>
X-Trace: 22 May 2012 11:21:18 -0700, 10.6.193.219
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.NT:1865
Article PK: 1130989


"Alex Schaft" <alexs@quicksoftware.co.za> wrote in message
news:4fbb459b@solutions.advantagedatabase.com...
> MAX_CACHE_MEMORY is not set in the registry. I found an article about
> LargeSystemCache at
> http://technet.microsoft.com/en-us/library/cc784562%28v=ws.10%29.aspx
>
> Seeing that server is only running Ads (along with file sharing for exe
> files and dll's), I've now switched that off, and will monitor

I am not familiar with that setting.

>
> I would think that on a big database it would be preferable to have
> minimal page faults and more data stored in ram than having it swapped
> out?
>

Yes, that would be the desired result. And, in theory, that should be the
behavior. I don't think a million page faults in 37 hours is excessive. A
page fault does not necessarily mean that there is a problem. For example,
a page fault occurs when memory is first allocated and accessed. And given
a page size of 4196, this means that it will take about 1 million page
faults simply to allocate and access 4 GB of memory. In other words, I do
not think it is possible to use 4GB of memory without incurring a million
page faults.

Mark Wilkins
Advantage R&D


Alex Schaft Posted on 2012-05-23 06:32:55.0Z
Date: Wed, 23 May 2012 08:32:55 +0200
From: Alex Schaft <alexs@quicksoftware.co.za>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.4) Gecko/20120421 Thunderbird/10.0.4
MIME-Version: 1.0
Newsgroups: Advantage.NT
Subject: Re: Memory question
References: <4fb9f71c@solutions.advantagedatabase.com> <4fba6521$1@solutions.advantagedatabase.com> <4fbb459b@solutions.advantagedatabase.com> <4fbbd91e$1@solutions.advantagedatabase.com>
In-Reply-To: <4fbbd91e$1@solutions.advantagedatabase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: 41.133.187.232
Message-ID: <4fbc8438$1@solutions.advantagedatabase.com>
X-Trace: 22 May 2012 23:31:20 -0700, 41.133.187.232
Lines: 55
Path: solutions.advantagedatabase.com
Xref: solutions.advantagedatabase.com Advantage.NT:1866
Article PK: 1130991


On 2012/05/22 20:22, Mark Wilkins wrote:
>
>
> "Alex Schaft" <alexs@quicksoftware.co.za> wrote in message
> news:4fbb459b@solutions.advantagedatabase.com...
>> MAX_CACHE_MEMORY is not set in the registry. I found an article about
>> LargeSystemCache at
>> http://technet.microsoft.com/en-us/library/cc784562%28v=ws.10%29.aspx
>>
>> Seeing that server is only running Ads (along with file sharing for
>> exe files and dll's), I've now switched that off, and will monitor
>
> I am not familiar with that setting.

Info here:
http://technet.microsoft.com/en-us/library/cc784562%28v=ws.10%29.aspx
>
>>
>> I would think that on a big database it would be preferable to have
>> minimal page faults and more data stored in ram than having it swapped
>> out?
>>
>
> Yes, that would be the desired result. And, in theory, that should be
> the behavior. I don't think a million page faults in 37 hours is
> excessive. A page fault does not necessarily mean that there is a
> problem. For example, a page fault occurs when memory is first allocated
> and accessed. And given a page size of 4196, this means that it will
> take about 1 million page faults simply to allocate and access 4 GB of
> memory. In other words, I do not think it is possible to use 4GB of
> memory without incurring a million page faults.
>

It seems that the task manager page faults lists all of them. Actual
disk reads are a lot less.

I'm still going to implement the reduced cache as per above, seeing as
how ADS only gets around 700MB of memory while 24GB are installed. More
memory available should increase performance I believe?

Server max had 200 users, 568 connections, 5353 work areas, 282 tables
and 540 data locks open after 3.5 days. Seeing how this is spread across
about 20 different applications, more memory for caching might be a good
thing :)

Regards,
Alex





> Mark Wilkins
> Advantage R&D