Performance Question

[Mark A]

"xixi" <dai_xi@yahoo.com> wrote in message
news:c0f33a17.0306261139.5b0de317@posting.google.c om...

> hello, i am using db2 udb v8.1 on NT, with db2jcc.jar as jdbc driver
> (type 4)
>
> 1. i create a view with where clause , so when i create sql reading
> the view, i don't need to build the where clause on the fly. so based
> on the performance, which is better? create a view with where clause
> or create a view without where clause but build the where clause when
> create the sql?
>

There will be an extra access to some of the catalog tables to resolve the
view. Even with the view, the difference may not be significant. If the
same statement is repeatedly submitted by the same thread, the access plan
will be cached and there will be no extra processing.

> 2. which one is better, open the result set once, return a big result
> set or frequently open , return a smaller result set
>

This depends on whether there is any user wait time (to scroll to the next
set that fits on the screen, etc.). If there is a good chance that the user
will not look at all the rows, then it might be better to fetch them in
batches as the user requests them.

> can you provide me some sql performance tuning tips or articles?
> thanks

To improve performance, I would get off NT and onto Windows 2000 or higher.

[Jake]

Hello,

I was wondering if there was a big performance enhancement using
commantype.storedprocedure opposed to commandtype.text in a webservice, or
what other benefits there would be with respect to scalability etc.. We are
using sql2k standard and planning on getting sql2k5 when it's released.
Thanks.

Jake

[Ken Dopierala Jr.]

Hi Jake,

You will definitely notice a performance increase using SPs. Also it will
help protect you from SQL Injection vulnerabilities. Finally, with VS.Net,
you can right click on your SP, run it with arguements, and even set
breakpoints. This is way cooler than trying to concatenate some long SQL
Query and playing around with the Query Analyzer to see if you got it right.
Good luck! Ken.

--
Ken Dopierala Jr.
For great ASP.Net web hosting try:
[url]http://www.webhost4life.com/default.asp?refid=Spinlight[/url]
If you sign up under me and need help, email me.

"Jake" <rondican@hotmail.com> wrote in message
news:u67dNq7pEHA.3688@TK2MSFTNGP09.phx.gbl...

> Hello,
>
> I was wondering if there was a big performance enhancement using
> commantype.storedprocedure opposed to commandtype.text in a webservice, or
> what other benefits there would be with respect to scalability etc.. We

are

> using sql2k standard and planning on getting sql2k5 when it's released.
> Thanks.
>
> Jake
>
>

[Lubomir]

Hi,

I would like to know your opinion about .NET menu server controls from
performance point of view.

It is a good idea if a menu is running on a client machine: a response is
quick and the server time is not used. However, implementation of a menu in a
java script often results in a messy source code, and there can be problems
if web browser on the client has disabled JavaScripts.

Menu implementation on the server side is clean and runs without problems in
a browser. However, it takes the server processor time and it needs to make a
route to the server and back every time a user hit a menu.

I gave a look at MSDN newsgroup page and it seems that MS used server-side
menu. It works fine (for me), even I don’t know how strong hardware was
necessary to use for achieving this performance.

What is your experience? Generally speaking, is it a good idea to implement
a menu in a form of a server side control?

Thanks,

Lubomir

[Steve C. Orr [MVP, MCSD]]

It's not like you have to choose one or the other.
You can mix and match server and client code to varying degrees depending on
what kind of menu you're trying to achieve.

Here are some free menu controls (many including source code) for you to
examine:
[url]http://msdn.microsoft.com/asp.net/?pull=/library/en-us/dnaspp/html/aspnet-buildmenuservercontrol.asp[/url]
[url]http://skmmenu.com/menu/[/url]
[url]http://www.titaniumsoft.net/tsweblib.aspx[/url]
[url]http://timothy.humphrey.name/thwc/[/url]
[url]http://At-Krays.Net/csharp.html[/url]
[url]http://www.obout.com/sm3/basic.aspx[/url]
[url]http://www.solpart.com/techcorner/SolpartMenuHistory.aspx[/url]
[url]http://www.dynamicdrive.com/dynamicindex1/[/url]

--
I hope this helps,
Steve C. Orr, MCSD, MVP
[url]http://SteveOrr.net[/url]


"Lubomir" <Lubomir@discussions.microsoft.com> wrote in message
news:C5B573B4-6153-40FC-AE26-992927C262D2@microsoft.com...

> Hi,
>
> I would like to know your opinion about .NET menu server controls from
> performance point of view.
>
> It is a good idea if a menu is running on a client machine: a response is
> quick and the server time is not used. However, implementation of a menu
> in a
> java script often results in a messy source code, and there can be
> problems
> if web browser on the client has disabled JavaScripts.
>
> Menu implementation on the server side is clean and runs without problems
> in
> a browser. However, it takes the server processor time and it needs to
> make a
> route to the server and back every time a user hit a menu.
>
> I gave a look at MSDN newsgroup page and it seems that MS used server-side
> menu. It works fine (for me), even I don't know how strong hardware was
> necessary to use for achieving this performance.
>
> What is your experience? Generally speaking, is it a good idea to
> implement
> a menu in a form of a server side control?
>
> Thanks,
>
> Lubomir
>

[DalePres]

Lubomir,

Keep in mind that all the menu controls, server generated or client
generated, will depend on the client allowing javascript. The primary
difference between the server controls and client controls is how the
javascript is generated.

For client-side menu controls, the javascript is generally either stored in
a script file that is included by using the src attribute of a Script tag or
by including the javascript directly in the HTML file. Server-side menu
controls, on the other hand, generally (but not always) create the
javascript from code in the application dll.

The main consideration I would use in determining whether to use client or
server side menu controls is whether the contents of the menu must be
created dynamically based on logic in your application. If the menu is
always consistent, use a client side control. If your menu contents must be
modified based on your business logic, then use server-side controls. In
fact, this consideration applies to all the controls on your page.

Keep in mind that neither client-side menu controls or server-side menu
controls are going to work if the client has javascript disabled.

HTH

DalePres
MCAD, MCDBA, MCSE

"Lubomir" <Lubomir@discussions.microsoft.com> wrote in message
news:C5B573B4-6153-40FC-AE26-992927C262D2@microsoft.com...

> Hi,
>
> I would like to know your opinion about .NET menu server controls from
> performance point of view.
>
> It is a good idea if a menu is running on a client machine: a response is
> quick and the server time is not used. However, implementation of a menu
> in a
> java script often results in a messy source code, and there can be
> problems
> if web browser on the client has disabled JavaScripts.
>
> Menu implementation on the server side is clean and runs without problems
> in
> a browser. However, it takes the server processor time and it needs to
> make a
> route to the server and back every time a user hit a menu.
>
> I gave a look at MSDN newsgroup page and it seems that MS used server-side
> menu. It works fine (for me), even I don't know how strong hardware was
> necessary to use for achieving this performance.
>
> What is your experience? Generally speaking, is it a good idea to
> implement
> a menu in a form of a server side control?
>
> Thanks,
>
> Lubomir
>

[Swd1974]

Say you have a table of users. Also a table of users that users have blocked

So as a user I can choose which users I wish to block and add them to the
blocked users table with my id and their id.

So when a user logs in what would be a good solution

Store all of the userid's the login user has blocked in a comma delimited list
in session. So if he conducts a search of users and I want to make sure as I
loop through them that thye are not blocked

or

do 2 loops when search results are displayed checking to make sure no blocked
users display?

I think storing the list would eb best but have read lists are very slow?

Imagine 2000 users on the site and searching at any given time.

Which choice is better?

Thx

[Pete Thomas]

To me a better solution would be to do a count left join on the blocked users
table in your user query SELECT u.* ,count(b.blockerid) as isblocked FROM
users ie LEFT JOIN blockeduser b ON users.userid = b.userid AND b.blockerid =
#thisuserid# Then just evaluate isblocked in a single loop