High Sierra Topix

One interesting thing I'm seeing while waiting for pages to load is in the feedback from the browser
"Waiting for www.highsierratopix.com"
"Waiting for highsierratopix.com"

It shows the first line, then the second line on (I assume) every wait state. I don't know if this is correct or redundancy.

response time getting progressively worse. 15-20 seconds for any page to load today. Was about 10 sec yesterday. Seems to be database related, as the background and header loads immediately, but anything that requires a query stalls

Sorry for not checking in sooner. It's been a really busy week at work and back home dealing with a 3.5 year old sick kid and an 18 month old with a broken collar bone.

Status of the slowness issue is that copeg and I think we have identified at least one source of the major problems if not the primary or only source. We don't think it's database related, rather there are a bunch of extra hooks in the code calling js files that either do not exist or are not necessary. We're working now to correct the issue and we really do appreciate everyone's wonderful patience while we attempt to juggle our personal lives with addressing bug fixes.

Cheers,
ERIC

Wait until they become teenagers LOL. Then, the fun really begins.

Jimr wrote:Wait until they become teenagers LOL. Then, the fun really begins.

...or when they move back in in their 20s

Required on-topic content: response time seems pretty good this morning, at least out here on the right coast.

ERIC wrote:Sorry for not checking in sooner. It's been a really busy week at work and back home dealing with a 3.5 year old sick kid and an 18 month old with a broken collar bone.

Status of the slowness issue is that copeg and I think we have identified at least one source of the major problems if not the primary or only source. We don't think it's database related, rather there are a bunch of extra hooks in the code calling js files that either do not exist or are not necessary. We're working now to correct the issue and we really do appreciate everyone's wonderful patience while we attempt to juggle our personal lives with addressing bug fixes.

Cheers,
ERIC

In Chrome, I'm running the Java console and watching the response time and failures. and i agree it's the js hooks. Not sure why CSS is throwing so much crap, but shouldn't that all be cached anyway even if you don't need it?

I love the java console. Firefox has a better one. I actually use it in my job to double check what our tool does for our corporate sites.

Still seeing 10-15 seconds on pages for the HST, which isn't bad, but not snappy. Keep up the good work, Eric and Greg!! It's much appreciated.

Russ

I removed some of those bogus hooks and will remove a few more tomorrow as I work my way through them to be sure I'm not removing anything that's essential. It does seem to be getting a bit better.

Any better now (speed-wise)?

ok.. now it's really snappy!! very nicely done. 7 seconds shaved off responses at least!

Russ

Good. I paid these guys to do the work so I wouldn't have to, but now I find myself fixing their sloppy codding (with Greg's help).