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.

NO FIX for CR#314222 on 12.5.0.3 (AIX) ?

2 posts in Product Futures Discussion Last posting was on 2004-01-27 14:28:53.0Z
Thomas Johansen Posted on 2004-01-27 13:48:15.0Z
Sender: 379b.40166bcc.1804289383@sybase.com
From: Thomas Johansen
Newsgroups: sybase.public.ase.product_futures_discussion
Subject: NO FIX for CR#314222 on 12.5.0.3 (AIX) ?
X-Mailer: WebNews to Mail Gateway v1.1s
Message-ID: <40166c1f.379e.846930886@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 27 Jan 2004 05:48:15 -0800
X-Trace: forums-1-dub 1075211295 10.22.241.41 (27 Jan 2004 05:48:15 -0800)
X-Original-Trace: 27 Jan 2004 05:48:15 -0800, 10.22.241.41
Lines: 16
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:1496
Article PK: 96505

Is it be possible to confirm that CR#314222 are NOT being
FIXED in any 12.5.0.3 EBF's ?

CR 314222
Title: MAXFD hardcoded on ASE to 2000
Description:
On IBM AIX and HP-UX platforms, the ASE-imposed limit of
2000 on the maximum available file descriptors has been
removed. This will enable more than 2000 user connections
per engine, unless limited by other factors such as memory
or the OS limit on file descriptors.

Is there any suggestion to a workaround for this problem on
12.5.0.3 (AIX), it is not yet possible for us to upgrade to
12.5.1 since the version is filled with other CR's which we
then runs into.


Bret Halford Posted on 2004-01-27 14:28:53.0Z
Message-ID: <401671C3.FAC666E5@sybase.com>
From: Bret Halford <bret@sybase.com>
Organization: Sybase, Inc.
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: en,ja
MIME-Version: 1.0
Newsgroups: sybase.public.ase.product_futures_discussion
To: Thomas@sybase.com, Johansen@sybase.com
Subject: Re: NO FIX for CR#314222 on 12.5.0.3 (AIX) ?
References: <40166c1f.379e.846930886@sybase.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Original-NNTP-Posting-Host: vpn-concord-155.sybase.com
X-Original-Trace: 27 Jan 2004 06:38:55 -0800, vpn-concord-155.sybase.com
Lines: 37
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 27 Jan 2004 06:12:25 -0800, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 27 Jan 2004 06:28:53 -0800
X-Trace: forums-1-dub 1075213733 10.22.108.75 (27 Jan 2004 06:28:53 -0800)
X-Original-Trace: 27 Jan 2004 06:28:53 -0800, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.product_futures_discussion:1497
Article PK: 96500


Thomas, Johansen wrote:
>
> Is it be possible to confirm that CR#314222 are NOT being
> FIXED in any 12.5.0.3 EBF's ?
>
> CR 314222
> Title: MAXFD hardcoded on ASE to 2000
> Description:
> On IBM AIX and HP-UX platforms, the ASE-imposed limit of
> 2000 on the maximum available file descriptors has been
> removed. This will enable more than 2000 user connections
> per engine, unless limited by other factors such as memory
> or the OS limit on file descriptors.
>
> Is there any suggestion to a workaround for this problem on
> 12.5.0.3 (AIX), it is not yet possible for us to upgrade to
> 12.5.1 since the version is filled with other CR's which we
> then runs into.

12.5.1 is the 12.5.x rollup that fixes CR 314222; it was not
fixed in any 12.5.0.3 ESDs.

Since file descriptors are a per-process (engine) limit, a
workaround may be to configure for more engines. Normally
(and for good reasons) ASE limits you to one engine per cpu,
however, if you are already at the maximum, and if
having more file descriptors is more important
to you than maximum performance, traceflag 1622 could be
used to remove this limitation. Performance can be expected
to degrade as engines will now spending cycles competing for
time on cpus and swapping in and out. If you use this
option, I recommend setting the sp_configure "runnable process
search count" to 1.

-bret