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.

ASA9 connec slow when open tables in the dabase

4 posts in General Discussion Last posting was on 2006-08-25 02:24:31.0Z
nn Posted on 2006-08-24 19:52:44.0Z
Sender: 7f5f.44ee0016.1804289383@sybase.com
From: nn
Newsgroups: ianywhere.public.general
Subject: ASA9 connec slow when open tables in the dabase
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <44ee038c.7fb5.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 24 Aug 2006 12:52:44 -0700
X-Trace: forums-1-dub 1156449164 10.22.241.41 (24 Aug 2006 12:52:44 -0700)
X-Original-Trace: 24 Aug 2006 12:52:44 -0700, 10.22.241.41
Lines: 8
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:5590
Article PK: 1619

I'm using ASA9.0.2. I was running normal but about a couple
weeks ago, it started running very very slow everytime I
want
to open a table from the Sybase Central or the ISQL. after
It
happened after I tried to open a dabase in the C:\Temp. Any
idea
I can get back the speed I used to have.


Greg Fenton Posted on 2006-08-24 21:36:59.0Z
From: Greg Fenton <greg.fenton@googles-mail-site>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: ASA9 connec slow when open tables in the dabase
References: <44ee038c.7fb5.1681692777@sybase.com>
In-Reply-To: <44ee038c.7fb5.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Original-NNTP-Posting-Host: wsp04839139wss.cr.net.cable.rogers.com
Message-ID: <44ee197d$1@forums-2-dub>
X-Original-Trace: 24 Aug 2006 14:26:21 -0700, wsp04839139wss.cr.net.cable.rogers.com
Lines: 43
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 24 Aug 2006 14:26:23 -0700, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 24 Aug 2006 14:36:59 -0700
X-Trace: forums-1-dub 1156455419 10.22.108.75 (24 Aug 2006 14:36:59 -0700)
X-Original-Trace: 24 Aug 2006 14:36:59 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:5591
Article PK: 1620


nn wrote:
> I'm using ASA9.0.2. I was running normal but about a couple
> weeks ago, it started running very very slow everytime I
> want
> to open a table from the Sybase Central or the ISQL. after
> It
> happened after I tried to open a dabase in the C:\Temp. Any
> idea
> I can get back the speed I used to have.

You will need to determine the actual cause of the slow down. It could
be the tools themselves, it could be the database, it could the client
connection (e.g. over a slow network?)

Is it the same table that is slow, or all tables?

I would recommend:

1. enable Request Level Logging
2. performing a "slow" operation
3. disabling Request Level Logging
4. run sa_get_request_times() and sa_get_request_profile().

After the above, analyze the contents of the tables satmp_request_times
and satmp_request_profile to determine if there are any "long running"
queries. If so, then it is a database problem. If not, then it is an
application problem (in this case, SC and/or ISQL).

If it is a database problem, post one or two of the long running queries
so we can take a look at what is causing the slow down.

Recognize that you are experiencing slow down at the UI layer. This
means that the slowdown can be anywhere from the UI down to the hardware:
UI<->asa client library<->asa server<->OS<->network/disk/memory/cpu

You need to spend time determining where that problem is. The Request
Level Log at least helps you determine if the problem is above or below
the client library.

g.f
--
Greg Fenton
Some Random Dude


nn Posted on 2006-08-25 00:58:29.0Z
Sender: 458.44ee4a68.1804289383@sybase.com
From: nn
Newsgroups: ianywhere.public.general
Subject: Re: ASA9 connec slow when open tables in the dabase
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <44ee4b35.45f.1681692777@sybase.com>
References: <44ee197d$1@forums-2-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 24 Aug 2006 17:58:29 -0700
X-Trace: forums-1-dub 1156467509 10.22.241.41 (24 Aug 2006 17:58:29 -0700)
X-Original-Trace: 24 Aug 2006 17:58:29 -0700, 10.22.241.41
Lines: 50
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:5593
Article PK: 1622

All the tables are slow not just a particular one.

> nn wrote:
> > I'm using ASA9.0.2. I was running normal but about a
> > couple weeks ago, it started running very very slow
> > everytime I want
> > to open a table from the Sybase Central or the ISQL.
> > after It
> > happened after I tried to open a dabase in the C:\Temp.
> > Any idea
> > I can get back the speed I used to have.
>
> You will need to determine the actual cause of the slow
> down. It could be the tools themselves, it could be the
> database, it could the client connection (e.g. over a
> slow network?)
>
> Is it the same table that is slow, or all tables?
>
> I would recommend:
>
> 1. enable Request Level Logging
> 2. performing a "slow" operation
> 3. disabling Request Level Logging
> 4. run sa_get_request_times() and
> sa_get_request_profile().
>
> After the above, analyze the contents of the tables
> satmp_request_times and satmp_request_profile to
> determine if there are any "long running" queries. If so
> , then it is a database problem. If not, then it is an
> application problem (in this case, SC and/or ISQL).
>
> If it is a database problem, post one or two of the long
> running queries so we can take a look at what is causing
> the slow down.
>
> Recognize that you are experiencing slow down at the UI
> layer. This means that the slowdown can be anywhere from
> the UI down to the hardware:
> UI<->asa client library<->asa
> server<->OS<->network/disk/memory/cpu
>
> You need to spend time determining where that problem is.
> The Request Level Log at least helps you determine if the
> problem is above or below the client library.
>
> g.f
> --
> Greg Fenton
> Some Random Dude


Greg Fenton Posted on 2006-08-25 02:24:31.0Z
From: Greg Fenton <greg.fenton@googles-mail-site>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: ASA9 connec slow when open tables in the dabase
References: <44ee197d$1@forums-2-dub> <44ee4b35.45f.1681692777@sybase.com>
In-Reply-To: <44ee4b35.45f.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Original-NNTP-Posting-Host: cpe00096b10fe8a-cm000f212f9e50.cpe.net.cable.rogers.com
Message-ID: <44ee5ce1@forums-2-dub>
X-Original-Trace: 24 Aug 2006 19:13:53 -0700, cpe00096b10fe8a-cm000f212f9e50.cpe.net.cable.rogers.com
Lines: 23
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 24 Aug 2006 19:13:55 -0700, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 24 Aug 2006 19:24:31 -0700
X-Trace: forums-1-dub 1156472671 10.22.108.75 (24 Aug 2006 19:24:31 -0700)
X-Original-Trace: 24 Aug 2006 19:24:31 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:5594
Article PK: 1623


nn wrote:
> All the tables are slow not just a particular one.

But that does not answer the question of where the problem is at.

Again, "slow" is what you are experiencing at the very top of the
application stack. There is no way to determine from the top of the
stack where the slowdown is.

My *guess* is that this is a database problem, possibly with bad
statistics, but there is no guarantee of that. You need to narrow down
the stack, and the request level log is a first step in that.

Once you have determined whether it is a slow running query, then you
can work on improving the performance of that query. But if it isn't
the query itself that is slow (i.e. the server is responding to the
requests rapidly), then you need to start looking at other areas where
there could be slowdowns (connection parameters, hardware, etc...)

g.f
--
Greg Fenton
Some Random Dude