Hi there -
on Media Temple, I see that the following is eating up too many resources
auntieowl.org/cornerstone-endpoint
I’m using X Version: 6.2.5 and a child theme. The site is up-to-date otherwise.
Help? thank you!
Hi there -
on Media Temple, I see that the following is eating up too many resources
auntieowl.org/cornerstone-endpoint
I’m using X Version: 6.2.5 and a child theme. The site is up-to-date otherwise.
Help? thank you!
Hello @tribalcore,
Thanks for asking.
Please take a look at solution mentioned in following thread and check with Media Temple:
Thanks.
Thank you! I’m trafficking this. Appreciate the quick reply.
You are most welcome.
Hi Prasant - I received this reply back from Media Temple. Any thoughts? The resource usage is killing me. I may have to pay $60 in overages on a $20 a month hosting account.
We will not disable any of our security features on the Grid-Service. If there is a specific security setting causing issues for your site, please provide us with an error message or any other information on the block/bottleneck you are inquiring about. We will investigate and do our best to assist.
Requests to /cornerstone-endpoint
are made when you are using the Content Builder or Theme Options. It’s how the application communicates with the server. Those requests can often use more resources because they are so frequent when you are actually working on the site.
To be honest, in the years our builder has been available I’ve never heard of this leading to “overages” charged on a hosting account. How are those overages being broken down? Are they charging you for extra bandwidth? If so it could be that you have some large files (images, videos) that are getting requested too many times. Are they saying /cornerstone-endpoint
is related to the overages? Or are you being warned that it’s too CPU intensive? If you could let us know a bit more about the technical nature of the resources being used we can give some more information from our end. Regretfully it isn’t likely that there is anything that can be done in the theme or Content Builder because of how /cornerstone-endpoint
is pretty much the communication path for everything while you are building your site.
Thanks for the quick reply! Yes, I am way over GPU limits, Media Temple’s measurement for “Grid Performance Unit”. See below - over 11,000 hits on a site that gets maybe 3 visits a day. After solving a cron issue on another domain, this is the only issue pushing me over the monthly limit. ¯_(ツ)_/¯
Hi @tribalcore,
You mean with 5% usage, you’re still reaching their limit? Perhaps your hosting plan is a shared one? In fact, GPU and CPU should be utilized 100%, it’s not the same as memory usage as the less the better.
And does that mean 11k hits per day? A page could issue about 120 requests (depends on the amount of content) average, and few of it is coming from cornerstone so it shouldn’t reach 11k. Perhaps something is calling it from outside like cron as you said? You can confirm that by using your browser developer tools (network tab) and you’ll see all requests made when you build a page using cornerstone.
Thanks!
Hi Rad - thank you for the reply. Yes, its shared hosting. It does appear that the site owner (my wife makes a lot of edits to her content. This seems to be causing the resource strain. Bummer, but that appears to be the issue. No it doesn’t seem to be a cron - that was for another domain. Thanks again.
Hi @tribalcore,
I see, that’s normal in a shared hosting as they limit your usage. Some are even limiting the requests to just 20 and throttle it. Hence, there is no problem with the requests, they are just wanting you to use less of the resources since it’s on the shared environment (multiple sites on the same machine sharing resources).
And even if you don’t use the builder or not even getting any traffic, your resources will still be eaten up by other sites sharing the same resources.
Unfortunately, there is no way to limit the connections as it depends on the content.
Thanks!
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.