|
Why might my OSQA website be running so slowly? I've had it take up to 23 seconds to load on a broadband connection. This site is also using the same hosting account and isn't running nearly that slow. Is there anything I can try to speed it up or resolve the problem?
showing 5 of 10
show 5 more comments
|
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- numbered list: 1. Foo 2. Bar
- to add a line break simply add two spaces to where you would like the new line to be.
- basic HTML tags are also supported
Tags:
Asked: 04 Aug '10, 02:45
Seen: 565 times
Last updated: 05 Aug '10, 09:21
yep very slow. What is your setup like?
I'm not exactly sure what sorts of things you're looking for. Could you be more specific?
If you run from python manage.py runserver, is it also slow? If not, it might have something to do with your apache setup. BTW, how did you make the box in the sidebar round corner? You changed the CSS?
Do you use mod_wsgi, mod_python, fastcgi or just plain cgi? Also, did you disabled cache in settings_local.py?
bbpan, if I do python manage.py runserver, I'm not sure exactly what that does. I tried it and it says, "Development server is running at http://127.0.0.1:8000/" Does that apply when I'm not hosting the website myself? And yes, I changed the CSS to round the corners.
Hernani, I'm using fastcgi. And I didn't disable cache in the settings if it wasn't disabled by default. I don't see any setting to make it so, except for disabled modules? And cache is not listed there.
I tried traceroute and the network doesn't seem to be the issue. If running python manage.py runserver is also fine, then I'm guess it's fastcgi in this case.
I guess python2.6 manage.py runserver is fine. I mean, nothing breaks, but I can't check it at http://127.0.0.1:8000/ since it's not hosted locally. Do you mean that fastcgi as such could be the problem and that I should look into something else? If so, what would be better?
If you run manage.py runserver <your.hosting.ip>:8000, you can connect to it even it's hosted elsewhere. If you don't specify the hosting IP or 0.0.0.0, it defaults to 127.0.0.1 and you can only connect to it locally. This is specific to django. I might be pointing you to the wrong direction, but what I was trying to do is to isolate the problem and make sure it's not a problem with django or the app first.
I put my website into debug mode and now it's running much faster. What does that mean...?
Really? After setting DEBUG to true it runs faster? It should be the other way around. But anyway, can you verify in the apache logs if the fastcgi threads dying very fast. Because if that is the case, that could mean that your site is restarting on every (or almost) request.