Speed on page loading

[RetroDreams]

It's this slow without most of the features?

[sivaganesh]

need to wait for another update..

[Hall of Famer]

umm I was wondering though, how does VB5 end up with 100+ queries? What was the number for VB4?

[digitalpoint]

umm I was wondering though, how does VB5 end up with 100+ queries? What was the number for VB4?

http://forums.digitalpoint.com/ needs 7 queries (as an example).

[Mark.B]

http://forums.digitalpoint.com/ needs 7 queries (as an example).

I'm disappointed in you Shawn, I'd have thought by now you'd at least have that down to zero, or even had it so it was in minus figures. Tsk.

[digitalpoint]

I'm disappointed in you Shawn, I'd have thought by now you'd at least have that down to zero, or even had it so it was in minus figures. Tsk.

Lol... I could actually probably get it down to around 4 if I *really* needed to... but 7 is perfectly workable. 100+... no.

[Paul M]

are you telling me that there's no way of reducing 117 queries?

He did not say that.

Whilst this may be so, this wouldn't even pass through my QA criteria, and I'm not even stringent.

It is not the resposibility of QA to determine how many queries a page should run.

[Lizard King]

It is not the resposibility of QA to determine how many queries a page should run.

I kindly don't agree with this as QA's main responsibility is making sure product is stable enough on every aspects. Of course Developers should have final word though if the script has major performance issues created by 100+ queries , they should not let that version pass QA.

[Allen Lin]

I kindly don't agree with this as QA's main responsibility is making sure product is stable enough on every aspects. Of course Developers should have final word though if the script has major performance issues created by 100+ queries , they should not let that version pass QA.

That's incorrect. QA's responsibilities are to assess and report on product stability, and to provide risk analysis to aid decision makers in risk management. In general, regardless of the company, QA does not have the power to schedule or delay releases. We test, analyze, prioritize, escalate, and verify.

[AlexanderT]

That's incorrect. QA's responsibilities are to assess and report on product stability, ...

Do you think product stability is guaranteed on a big forum with 110+ queries per page view? If they're to report on product stability, it'd be illogical to ignore query count (and performance in general).

[Stallyon]

Remember how many queries vB4 had when it was first released to the public? I think it was over 100 queries until it was optimised?

[AlexanderT]

Remember how many queries vB4 had when it was first released to the public? I think it was over 100 queries until it was optimised?

I also remember the long debates trying to convince us that the number of queries is irrelevant as long as they are all optimized.

[Lizard King]

That's incorrect. QA's responsibilities are to assess and report on product stability, and to provide risk analysis to aid decision makers in risk management. In general, regardless of the company, QA does not have the power to schedule or delay releases. We test, analyze, prioritize, escalate, and verify.

I am sorry but i again will like to disagree. In companies i worked for ( not IB ) QA had power to stop a release. Maybe there is an issue with the workflow in IB and it actually maybe should discussed more. 2 major version release : 2 epic fail...

[Mark.B]

I am sorry but i again will like to disagree. In companies i worked for ( not IB ) QA had power to stop a release. Maybe there is an issue with the workflow in IB and it actually maybe should discussed more. 2 major version release : 2 epic fail...

Where I work QA certainly can't stop a release. They can decline to sign it off, then management take a decision on whether to press on anyway or not. Sometimes they do, sometimes they don't.

[Zachery]

I am sorry but i again will like to disagree. In companies i worked for ( not IB ) QA had power to stop a release. Maybe there is an issue with the workflow in IB and it actually maybe should discussed more. 2 major version release : 2 epic fail...

Then you are by far the large exception to the industry. I'm not aware of any large software houses where QA can say NO, and anyone would fullstop a release.