Speed issue

[skc]

I have created a website for a car dealer, where I have
two search options:

1. View all cars
2. Search for a car using a variety of options

Trouble is, the View all cars option takes absolutely ages
to download the cars from my Access2000 table to the DRW
on my asp page.

I have indexed the table, but I am now blowing my brains
out as the uploadability of cars takes a long time!!!

Search using dropdowns which fires WHERE clauses at my DRW
is not so bad.

Please can someone help me on this one.

website is: www.maslenmotors.com, click the showroom tab
at the top.

skc

 

[Thomas A. Rowe]

1. If using the DRW, consider learning to hand code your ASP which help
speed up the results.

2. Reduce the use of any calculations being done when displaying, instead
have the value calculate when the record is created, so that you only have
display the data.

3. Limit the results to 10 per page with paging per group of 10, etc. This
will help as more records are added and avoid the script timing out as the
database grows.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================

 

[skc]

see inline

-----Original Message-----
1. If using the DRW, consider learning to hand code your ASP which help
speed up the results.

What do you mean by that? For my "View all vehicles"
button, you will notice that I am passing Make="Make is
Not Null", Transmission="Transmission is not null" etc...
which in my DRW equates to SELECT * FROM x WHERE ::Make::
AND ::Transmission::

Is that wrong? Maybe my SQL needs tweaking, as the
selective drop-down menu works very quickly - I still do
not understand it!

2. Reduce the use of any calculations being done when displaying, instead
have the value calculate when the record is created, so that you only have
display the data.

The calculations are just a bit of ASP script, where I

3. Limit the results to 10 per page with paging per group of 10, etc. This
will help as more records are added and avoid the script timing out as the
database grows.

If I limit it to 10 per page, this will look a bit
rubbish! What is the script timeout? How can I find out
about this?

 

[MD WebsUnlimited.com]

It took under a min for the query to return and display all records (56)

 

[Thomas A. Rowe]

Mike,

On a dial-up connection, that may timeout, as well if the number of items in
inventory increases over time.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================

 

[Thomas A. Rowe]

See below.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================

see inline


What do you mean by that? For my "View all vehicles"
button, you will notice that I am passing Make="Make is
Not Null", Transmission="Transmission is not null" etc...
which in my DRW equates to SELECT * FROM x WHERE ::Make::
AND ::Transmission::

Is that wrong? Maybe my SQL needs tweaking, as the
selective drop-down menu works very quickly - I still do
not understand it!

Use the FP DRW, the code is somewhat bloated (as FP needs to be able to
maintain it), normally when you hand code, you can accomplish the same thing
and more with less code.

The calculations are just a bit of ASP script, where I
import a DRW parameter <% FP_FieldVal(fp_rs,"... %> and do
some +,-,/ operations on it.

Using +,-,/, can slow down the display of the query. My suggestion is that
these operation are done when the item is added to the database, so that
they are just display when a query is run.

If I limit it to 10 per page, this will look a bit
rubbish! What is the script timeout? How can I find out
about this?

Do a Search for ASP Script Timeout. However the default is 90 seconds, I
strong recommend that you do not change this, unless you are running on your
own server.

How about returning less info when do a full listing, then let the user
click on a link to see more details about the item

 

[skc]

Mike,

I know it takes under a minute...but it is damn slow
compared to doing a filter ...WHERE something=something
query.

Any ideas on speeding this up?

skc

 

[skc]

Thomas,

I tested this on a dial-up V90, and it does not timeout
(luckily!).

I had no idea of this timeout thing...I will have to have
a go at returning maybe 10 records a page or something
similar.

Mind you...the whole emphasis of this is to let the user
see all cars so that they can make a choice.

skc

 

[Thomas A. Rowe]

SKC,

With 56 records, I don't expect it to timeout, however as the number of
records increases, so do the chance of a timeout at some point.

How about just displaying the photo of the car and a few basic details with
a link to more details for each listing, then you could return may be 25
cars per page.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, Forums, WebCircle,
MS KB Quick Links, etc.
==============================================

 

[Tom Miller]

I am not experience here, but if part of the issue is the band-width, would
doing thumb-nails with click to enlarge help? ala Photogallery?

Tom Miller

Mike,

I know it takes under a minute...but it is damn slow
compared to doing a filter ...WHERE something=something
query.

Any ideas on speeding this up?

skc

--
+++++++++++
I provide computer tech support for North East Kansas: www.bluecollarcc.com
100,000's of files are at: www.chatnfiles.com
Some the best free Website creation training on the Web at:
www.w3schools.com