DRT Page Loading Time

jcgriff2

jcgriff2

Co-Founder / Admin
BSOD Instructor/Expert
Microsoft MVP (Ret.)
Staff member
Joined
Feb 19, 2012
Posts
21,541
Location
New Jersey Shore
Is there anything that can be done to hasten the DRT page load?

I just timed it - about 20+ seconds before it appears; then another 5-10 seconds after that before you can search the page (CTRL-F) or scroll. While waiting for the page to load, you think of all the other things you could be doing at that time. I know that 20-30 seconds may seem to be not that long -- until you're sitting there waiting for it!

I believe we have just over 4,000 drivers/entries in the SQL table as of today.

For those that don't know -- the DRT is made up of an SQL DB + (mostly) PHP, written very, very quickly over a week or two period back in ~January 2010. The public only sees a small portion of the DRT HTML output. The majority of it is a back-end Administrator's area that works just fine.

It was lightening fast in the beginning, but we only had 500-750 drivers then.

Thanks,

John
 
Last edited:
Your best bet is to limit the number of drivers returned on the main page.

Either restructure it to a tab based system where it only shows ~50 per tab.

Or switch it to use some Async scripting and grab the extra data as you scroll or as you navigate around.

FWIW, even without caching of any kind all my load times are <3 sec
 
My load time is a lot faster than what is being reported here (nearly instant). Could it vary by browser? What about hardware, e.g. SSD?
 
Yeah - I thought about limiting the results on the main page, but then that would defeat the way I use it.

Once the table is loaded, I then do a find (CTRL-F) for the driver name I'm after. If the main page is split up into x-number of pages, then I have to do multiple searches (1 for each page). I could try the DRT's search function -- but to do so requires you to be on the main DRT page.

What if for Sysnative's DRT mirror, we list the driver name only - no info column; no update column. Then at the top of the table, have a link to bring up the current version.

how much time do you think we would save (out of the 20-30 seconds) if we just had a listing of hyper-linked driver names only?

What is the most resource intensive part of loading and displaying the current DRT? Is it -
  1. Reading the SQL DB?
  2. Writing the SQL DB to the HTML file?
  3. Sorting the DRT SQL DB?
  4. Some other item that I missed?

There must be a reason that the loading and display of the DRT is so slow as I've worked with other SQL DBs that contain a ton more data and brings it up much faster. I guess a good example of this is our vBulletin forum site itself.

Are there any changes that you would recommend to the code to make things load faster? If you give me a hint, I can look into it.

The current DRT was written over 7 years ago and in a huge rush. Although we had some specs written out, you really didn't know what Carrona and I wanted, Geoff. Had we taken the weeks or even months that a project of this size should have been allocated to cover all bases, perhaps we would not have a 1/2-minute DRT load time as of today. Who really knows.

Thanks for any help with this - much appreciated.

John


@ Carrona - My proposal is for Sysnative's DRT mirror only. NO CHANGES would be made to Carrona.org DRT without your permission, of course.



`
 
There might be a way for us to re-write some of the code to load the tables much faster. If we're only editing the main table page, it probably wouldn't be that much work.

I can take a shot at it, but I'll need a bit of time to re-familiarise myself with it.
 
It is literally just dumping a table and doing some formatting.

We might be able to do some caching magic to reduce load times.

Everything works fine for me though. 3 seconds to load it from scratch is not bad at all.
 
It takes here literally 2 seconds from the moment I press enter in the URL to the page completely loaded.
 
Loads in ~3 seconds here, Pale Moonx64, SSD and mediocre shared connection:

Speed Test History
Date/Time Avg Down Avg Up
18-08-2017 09:19:11 (GMT) 13.8 Mbps 1.4 Mbps
16-08-2017 15:20:18 (GMT) 13.0 Mbps 1.6 Mbps
16-08-2017 15:17:04 (GMT) 9.4 Mbps 1.6 Mbps
13-08-2017 22:55:56 (GMT) 11.3 Mbps 1.1 Mbps
08-08-2017 13:06:04 (GMT) 13.1 Mbps 1.6 Mbps
03-08-2017 11:56:31 (GMT) 13.5 Mbps 1.3 Mbps
02-08-2017 16:51:48 (GMT) 13.3 Mbps 0.8 Mbps
31-07-2017 12:55:35 (GMT) 14.9 Mbps 1.6 Mbps
27-07-2017 13:04:45 (GMT) 15.4 Mbps 1.5 Mbps
Click to expand...

About:memory 37.08 MB (02.85%) -- top(Driver Reference Table, id=14441)


Edit: took way longer to upload this reply ~5-6 seconds.
 
I'm not having any speed issues. Could it be your ISP?
I had been working on the DRT (if you look at the TempDB you'll see a lot of date/time stamps that I'm using to update the Windows drivers)
I messed with a file in the bulk upload so I wouldn't have to look up/type the driver descriptions (not a good thing and I won't do it again - it's too work intensive for even the 25 drivers that I was trying to add)
EDIT: I get notified (by email) if carrona.org goes down, but don't know about slowdowns. It seemed very responsive yesterday when I was updating the Windows drivers. We'll see how it goes today ('ll be starting after I post this).


Would renaming the page(s) affect the BSOD Processing App (particularly the dvrref.php page)?

If not, then the dvrref.php page could be renamed (for example) to alldrt.php
And then the dvrref.php page could have only the quick links and maybe a little blurb, a link to alldrt.php, and a note that loading times will be great?
Still, many of the quick link entries will have a couple of hundred drivers listed - but that's better than the entire 4000+

ANOTHER EDIT: How about a little housekeeping? We can delete the dynamic drivers that were entered for Daemon Tools and the one's for MSSE/Windows Defender. That'll cull several hundred from the table (and, as an aside, will make the total count a bit more realistic).
 
Are all of you telling me that the DRT loads and you have full control over the page in only a few seconds?

By "control of the page" -- I mean that you can press CTRL-F and enter a driver name.

Try it. Click on the link below for the DRT, then CTRL-F, then enter sptd.sys

The entire table - Driver Reference Table

Please make sure it is not in your cache anywhere.

It takes 15-25+ seconds from the time I click on a DRT main page link to have control of the page to do a search.

I have tested this on many different systems; different networks - always the same 15+ second MINIMUM.

The current size of the table that downloads to my IE cache folders - 1,767,948 bytes.
 
Last edited:
If it helps, I've made a screenshot of my load time in incognito.
Sometimes it's 1.8 second, usually 2.4

loading time.jpg
 
jcgriff2 said:
Are all of you telling me that the DRT loads and you have full control over the page in only a few seconds?

By "control of the page" -- I mean that you can press CTRL-F and enter a driver name.

Try it. Click on the link below for the DRT, then CTRL-F, then enter sptd.sys

The entire table - Driver Reference Table

Please make sure it is not in your cache anywhere.

It takes 15-25+ seconds from the time I click on a DRT main page link to have control of the page to do a search.

I have tested this on many different systems; different networks - always the same 15+ second MINIMUM.

The current size of the table that downloads to my IE cache folders - 1,767,948 bytes.
Click to expand...

This system hadn't opened the DRT yet. It still loaded in 0.5-1.5 seconds, and I could search for sptd.sys as soon as I could see the list.

I tested yesterday in a private browsing session to make sure I wasn't pulling from a cache. Again, 0.5-1.5 seconds each time.

I'm using Microsoft Edge in these tests, and all my systems I've tested on have an SSD. This current system has a M.2 SSD, which means it's probably the fastest to cache. I'll check on my 5400 RPM system ...


On the 5400 RPM system through Microsoft Edge, I see a load time of 2-3 seconds.
Internet Explorer takes 4-5 seconds on the same system.
Mozilla Firefox takes 7-8 seconds on the same system.
Google Chrome takes 3-4 seconds on the same system.
 
After clearing the Pale Moon cache and me fumbling around the keyboard in the dark it still loaded in ~4 seconds.
 
I tried private browsing on Pale Moon - but the search autofill seems linked (so I'm unsure of what I'm doing).
The search box comes up within a second or two, while the search results are almost immediate.

Have you compared the Sysnative mirror to the Carrona mirror?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top