page load times in v6.2

[Infopro]

I'm not taking jabs at you. I'm unable to keep up with you on this issue though, we're heading into 3 pages here me and you. I do want to comment on this:

 

I love how that's the measuring stick for WHMCS to justify looking into an issue. Unless the sky is falling, who cares right?

 

This is incorrect. WHMCS Technical Support did discuss this with you and provided suggestions. Also, back in February in that ticket, John explained to you what the differences are between 5.x and 6.x:

 

The load time of pages in WHMCS v6 will take longer as there is more data presented. The shopping cart has to be queried to obtain the item count and displayed in the top-right corner, on the homepage the announcements section has to be queried to display the announcements, on the ticket submission page the tickets history has to be queries to populate the "Your Recent Tickets" sidebar. The "Notifications" are are also loaded on each page load as well.

 

We hope that you find these new features beneficial.

 

I've already read your reply to that, so no need to reply again here.

 

What I don't understand is the need to make this a sky is falling issue. Going only on that comment by John about new features you don't like or want, instead of complaining about 600ms speed issues, shouldn't you be asking instead about how to turn off these new things you dislike that slow you down 600MS per page load?

 

Without selectively quoting you, I have to ask, why all the hostility over this right out of the gate in that ticket and this thread?

[Serenade]

What I don't understand is the need to make this a sky is falling issue.

 

It's not a sky is falling issue, the only reason the conversation has gotten to this point is direct result of the refusal to investigate the root of the problem, or even bringing the issue up to someone who could do anything about it.

 

Going only on that comment by John about new features you don't like or want, instead of complaining about 600ms speed issues, shouldn't you be asking instead about how to turn off these new things you dislike that slow you down 600MS per page load?

 

I'm not asking how to turn those features off because they are not the cause of the slow down, and I can say this with absolute certainty since I was already informed by your staff switching the WHMCS 5 template would disable said features. As I've mentioned time and time again, the slow down remains using the WHMCS 5 template on v6 and there is no increase in performance doing while running it.

 

Without selectively quoting you, I have to ask, why all the hostility over this right out of the gate in that ticket and this thread?

 

The hostility (if that's what you want to call it, I'd call it frustration) hasn't come right of the gate. I submitted a very civilized support ticket two months prior to the one you saw (#BGY-029300) and I was given the same run around and dismissive replies basically saying "that's just the way it is" in v6.

[Infopro]

Selectively quoting you:

 

...

 

The hostility (if that's what you want to call it, I'd call it frustration) hasn't come right of the gate. I submitted a very civilized support ticket two months prior to the one you saw (#BGY-029300) and I was given the same run around and dismissive replies basically saying "that's just the way it is" in v6.

 

I'm not sure I'd call that civil, your first post in that ticket was nothing but a link to this thread, back when it had a more harsh title than it does now. 2 replies in, you resorted to all CAPS there as well.

 

 

It's not a sky is falling issue, the only reason the conversation has gotten to this point...

 

It "got here" when you reported the issue by opening a ticket and simply linking to this thread, where you posted that you find an almost 600ms slow down between versions:

 

This is incredibly disappointing.

 

Version 5.3.14, has a clientarea.php GET request of 164ms

 

Version 6.2, has a clientarea.php GET request of 709ms.

 

And in that ticket you wanted an investigation and ticket escalation right away, but didn't get one.

 

...

is direct result of the refusal to investigate the root of the problem, or even bringing the issue up to someone who could do anything about it.

 

You did get explanations, details and suggestions though. Across multiple tickets for the same reported issue.

 

It's been at this point right from the start of your discovery of the extra 600ms.

 

When you open a ticket and report that you may have found an issue with pages loading slower, or whatever else you might report, that report is noted and tracked and added to a list of reports from others for closer review as needed at a later date. That earlier ticket, last reply from John basically states this.

 

One ticket with one link in it to one thread with a harsh sounding title does not motivate the development team to come pick apart the software to solve the issue that one person seems to be having an issue with. And you shouldn't get frustrated about it when you find that out, I don't think.

 

I have no idea as I'm not Technical Support as to how many others have opened tickets like you have and reported this issue, but if there are others, I'm sure they'll look into it, do the investigation you wanted, and do the needful in a future update, if needed.

 

So my question remains, what is it about this 600ms slow down you're dealing with and reported on, that's making you so frustrated?

[Serenade]

I'm not sure I'd call that civil, your first post in that ticket was nothing but a link to this thread, back when it had a more harsh title than it does now. 2 replies in, you resorted to all CAPS there as well.

 

Garbage page loads times was a perfect representation of the issue, harsh or not. There's no justification for a 600ms slowdown following a software update.

 

It "got here" when you reported the issue by opening a ticket and simply linking to this thread, where you posted that you find an almost 600ms slow down between versions:

 

It's been at this point right from the start of your discovery of the extra 600ms.

 

The proverbial here and at this point are specifically referring to the useless back and forth that now populates two pages of this thread, which has since resorted to you accusing me of not being nice enough while reporting an issue which shouldn't have happened to begin with if a shred a quality assurance took place.

 

You did get explanations, details and suggestions though. Across multiple tickets for the same reported issue.

 

The "explanations" I received which have now been covered in detail throughout this thread are of no use, nor in my opinion bore any relevancy to the issue. The "suggestions" I received were followed, and did nothing to address the issue.

 

When you open a ticket and report that you may have found an issue with pages loading slower, or whatever else you might report, that report is noted and tracked and added to a list of reports from others for closer review as needed at a later date. That earlier ticket, last reply from John basically states this.

 

That last ticket, perhaps. However it doesn't inspire a whole lot of confidence said investigation will take place when the subsequent conversations have revolved around "it's your server's fault", "that's cause you're using a custom template" and "that's because of new feature X and Y".

 

One ticket with one link in it to one thread with a harsh sounding title does not motivate the development team to come pick apart the software to solve the issue that one person seems to be having an issue with. And you shouldn't get frustrated about it when you find that out, I don't think.

 

So my question remains, what is it about this 600ms slow down you're dealing with and reported on, that's making you so frustrated?

 

Whether I report the issue on a silver platter or not shouldn't matter. Whether you think a 600ms slow down with updated software is a big deal or warrants getting frustrated about does not matter.

 

Two pages into this thread, the fact remains:

 

There is a 600ms slowdown from WHMCS 5 to WHMCS 6 using the same templates on both. The slowdown is not caused by new features in WHMCS 6, since the WHMCS 5 template doesn't use those features. I think everything that could possibly be said besides actually fixing the issue has been said, and we can leave it at that until if and when an update comes out fixing the issue. Since none of the developers have yet to be flagged on the issue, that's unlikely to happen but I suppose you never know.

[cloferba]

Garbage page loads times was a perfect representation of the issue, harsh or not. There's no justification for a 600ms slowdown following a software update. The proverbial here and at this point are specifically referring to the useless back and forth that now populates two pages of this thread, which has since resorted to you accusing me of not being nice enough while reporting an issue which shouldn't have happened to begin with if a shred a quality assurance took place. The "explanations" I received which have now been covered in detail throughout this thread are of no use, nor in my opinion bore any relevancy to the issue. The "suggestions" I received were followed, and did nothing to address the issue. That last ticket, perhaps. However it doesn't inspire a whole lot of confidence said investigation will take place when the subsequent conversations have revolved around "it's your server's fault", "that's cause you're using a custom template" and "that's because of new feature X and Y". Whether I report the issue on a silver platter or not shouldn't matter. Whether you think a 600ms slow down with updated software is a big deal or warrants getting frustrated about does not matter. Two pages into this thread, the fact remains: There is a 600ms slowdown from WHMCS 5 to WHMCS 6 using the same templates on both. The slowdown is not caused by new features in WHMCS 6, since the WHMCS 5 template doesn't use those features. I think everything that could possibly be said besides actually fixing the issue has been said, and we can leave it at that until if and when an update comes out fixing the issue. Since none of the developers have yet to be flagged on the issue, that's unlikely to happen but I suppose you never know.

Hi Serenade

Please let me know which versions you are comparing. I'll download them and set them up on a Linode VPS to check the loading speed. Let's see if it's your or WHMCS fault

[Infopro]

Hi Serenade

Please let me know which versions you are comparing. I'll download them and set them up on a Linode VPS to check the loading speed. Let's see if it's your or WHMCS fault

 

That's sure friendly of you. If you've read the thread, the question you ask is already answered though.

[Serenade]

Hi Serenade

Please let me know which versions you are comparing. I'll download them and set them up on a Linode VPS to check the loading speed. Let's see if it's your or WHMCS fault

 

Hey cloferba. The versions are 5.3.14, and version 6.2.

[cloferba]

Unfortunately it has to be installed on the same server IP. I'll be happy to install the latest WHMCS version if you provide me a licence associated to 139.162.47.121

I'll be testing this VPS for 13 days.