phaider
Posts: 37
|
| Posted: 09/27/2004, 8:43 AM |
|
Hello Forum,
one of my "bigger" page has about 250kb (3 forms inside, no includable page). My personal feeling is, that the page processing is not fast. Has anyone experiance or maybe the same impression? What would be the best way? For example to divide into separated pages, working with includable pages or any tip to reduce the .asp file size?
Best regards
Peter Haider
|
 |
 |
DonB
|
| Posted: 09/27/2004, 8:26 PM |
|
If you are doing a lot of DLookups, that can be a significant impact -
particularly if each one involves a separate "new clsDBconnection"
statement. The data sources should be analyzed to be sure they are as fast
as possible (table scans vs. indexed-lookups).
Beyond that, 250K is pretty sizable for one page. I'd hate to be forced to
access it via a dialup line.
Page speed is good to excellent in all my experience.
--
DonB
http://www.gotodon.com/ccbth
"phaider" <phaider@forum.codecharge> wrote in message
news:641583527057c3@news.codecharge.com...
> Hello Forum,
>
> one of my "bigger" page has about 250kb (3 forms inside, no includable
page).
> My personal feeling is, that the page processing is not fast. Has anyone
> experiance or maybe the same impression? What would be the best way? For
> example to divide into separated pages, working with includable pages or
any
> tip to reduce the .asp file size?
>
> Best regards
>
> Peter Haider
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.codecharge.com/
>
|
|
|
|
BlinkyBill
Posts: 86
|
| Posted: 09/28/2004, 5:16 AM |
|
Just some followup comments:
As Don said analyse your queries, if your using SQL Server run the profiler to see whats happenning. Make sure you are using indexes.
Also with page size, if your pages are getting large use GZIP encoding, using XCaches GZIP encoded I got 300K html source down to around 40K by using it to enable GZIP encoding and getting to do things like removing all white spaces in HTML (they take space)
Microsoft has a debugging proxy that is also useful for looking at HTML file sizes, it 's called Fidler.
http://www.fiddlertool.com/
|
|
|
|
peterr
Posts: 5971
|
| Posted: 09/28/2004, 5:35 AM |
|
I'm not sure why your ASP code is so large, but I don't agree that the code size is important here. We've done some testing with loading and executing huge ASP code files and they were loaded very fast, possibly couple % slower than smaller file sizes. Large file size is just the result of other things that can slow down your Website's performance. For example having big forms with a lot of controls and large HTML template size can result in slow performance, even if your HTML size is much smaller than 250KB, let's say 50KB. Some of the performance issues could be related to the client (browser) that needs to display all the controls, which consumes memory and requires processing time. On the server, a small ASP program may take long time to process large HTML templates. I'd recommend splitting your page into multiple ones if possible.
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
|
