I have an existing django 3.0 project that I've integrated Wagtail 2.10.2 into. Wagtail seems to be working ok but the wagtail admin is super slow. The user facing pages themselves are fine.
Django debug toolbar shows that the delay is due to the browser request taking 5 - 8 seconds for each page load. The time panel shows 74601 involuntary context switches (5 voluntary.)
This is happening on a localserver. I have only a handful of wagtail page objects and the database size is small.
I've run collectstatic and all the GET requests are either 200 or 304.
Can anyone help?
Following tomd's suggestion, I disabled django debug toolbar and the problem is resolved. See the links in his comments.
Related
I have started working on an Angular 10 application using DevExtreme UI Widgets. I deployed a demo version in our Azure Cloud but while I was playing with it, I noticed a strange behavior. It seems that I lose my styles when I refresh.
For example, this is how the login page should be displayed:
If I refresh the URL without entering my login credentials, the page changes and gets displayed like this:
When I login, the bad or good styles are carried over. For example, the landing page should be displayed like this:
If I refresh the screen here, I also see the styles being altered. This is how the landing page gets displayed when the styling is lost:
When I lose the styling if I keep refreshing the page over and over again, eventually I regain the styles and my application starts being displayed as intended.
Any idea what causes the styles to be lost? Any suggestion would be greatly appreciated.
Thanks,
Ed
Regarding the deployment of Angular projects, I have encountered various problems. I am willing to share it with you and hope it will help you.
Troubleshooting steps:
Solution 1.
You can deploy it via Azure Pipelines CI/CD without using the vscode to deploy webapp.
Maybe smth wrong with VS Code plugin, as it is in preview
Solution 2.
Use github for continuous deployment. It is recommended to create a webapp and choose the Linux operating system.
Solution 3.
It is recommended to use FTP to publish the build folder after the project npm build.
This issue was resolved. After further investigation, it turns out that the problem had nothing to do with Azure Cloud deployment. I use DevExtreme UI widgets in my application and the application is based on their Angular Template.
I tried the website using Chrome, Edge and Firefox. The issue described above only happened in Chrome. DevExpress tech support pointed me to this support ticket.
After following the recommendations in the workaround and a redeployment, my app looks fine even in Chrome.
Thanks for everyone trying to help.
Ed
I have a WordPress site hosted in a server. I also verified the server configs everything is perfect. No space or ram issues.
When I start to load my site URL. In my networks tab, I see that the first request was "instant-loan/" which took 1min and rest all requests come faster after that. Ofcourse they loaded from cache in the image I shared but if I open in incognito also the rest of the requests are in miliseconds. This happens in all pages,
What could be the issue here? I have been searching for a possible cause for a very long time.
I have performed a site performance test in google insights and GT. They both gave the same below results:
Page loading: 35sec.
They only say to optimize images and js content.
The total page size is 6mb.
214 requests are beeing processed.
[NEW EDIT]
Below is the performance result. It shows a lot of idle time and js image rendering seems to happen quite fast. A max of 4 sec to render, load the site. Thus I assume there is something wrong with the server. I have minified CSS and JS. Also, use compressed images only. Is this because of any mysql connection issue ?? Has anyone faced it?
I've got a high traffic blog (300,000 pageviews per day) made with asp.net that uses output cache for article pages.
It usually works well, but many users have complained about being prompted to download the page instead of being shown the page on the browser. I've seen it myself too a couple of times.. it goes away only when the cache for that page is refreshed.
It happens with II7 and below, using both .NET 4.0 and 2.0 (I recently updated the framework's version and the problem continues).
Any idea why?
I finally found the answer to my problem.
In case anyone else is interested, the problem was that, sometimes, pages were cached after a request made by a mobile user. For some reason, IIS sends back the response type as WML instead of text/html in that case, which is only accepted by some mobile browsers, not desktop.
Here's the simple solution for it:
Make IIS not render pages as WML. Ever!
Ive an asp.net 4.0, c# site,
all the functionality works fine apart from one thing which is doing my head in.
I have 3 image buttons on the masterpage which link to the clients facebook, linkd in and twitter pages,
when I run it on my dev machine (IE 8) the open fine,
when I make the site live (IIS 6) they dontr appear to do anything, no error, no redirect, nothing in the event log.
I was about to bin them and do them from scratch but im wary that I'll install it and the same thing will happen - anything obvious I should check?
thanks
Did you checked whether you missed deploying any external CSS files or images if there are any which effectively causes image buttons to get hidden/unidentifiable?
Situation:
Varnish 2.1.4 lenny (latest stable) is running succesfully on Debian/Apache with mod_php.
I've got multiple Drupal sites running on this server and some are Varnish enhanced (e.g. using Pressflow). These sites work as expected.
The other sites, who aren't using the reverse-proxy, load fine when you enter the address or click around but take a really weird long time (30-45 secs) to load when you refresh the page using F5 or Ctrl+F5.
I don't think it's a VCL configuration thing; if I do a return (pass) immeditaley for one of these domains, the problem persists. Could this be related to this issue?
Are the sites that arn't using varnish still going through it?
For debugging, I would have a look at the net tab with firebug, it should give you an indication of what is taking its' time. It could be that the itial page load is fine but the other resources are taking a long time to get through.
Actually, I found out varnish 2.1.4 has some kind of problem with Apache's Keep-Alive functionalitiy (which was On). Turning it Off solved both problems!