ndavies Posted October 2, 2009 Posted October 2, 2009 Ok chaps, we're hosting a Moodle on site, and when I'm at home it's nice and fast and usable.. when i'm in school watching classes use it, it's deathly slow. we've got an ISA server which all traffic goes through, despite the fact the moodle server is on the network, I think requests to and from the moodle server are going to the router to come back in again is there any optimisation stuff to make it run faster or better set up methods i.e. when in school, get it locally rather than go out to come back in. cheers Nick
webman Posted October 2, 2009 Posted October 2, 2009 Can you add some sort of exclusion that would stop internal requests for the Moodle box going via ISA? Also, what web server software is Moodle running under? Replacing Apache with Lighttpd+Xcache got me a 200%+ speed increase (in terms of requests per second), for example. 1
Guest Guest Posted October 2, 2009 Posted October 2, 2009 Do a tracert and find out if it is going via ISA. Just make a host pointer in your DNS to point directly at the moodle box.
p858snake Posted October 2, 2009 Posted October 2, 2009 Most browsers can be told not to use the proxy for certain addresses. eg: Firefox: Options > Advanced > Network > Settings IE: Internet Options > Connections > LAN Settings > Proxy Settings > Advanced 1
ndavies Posted October 2, 2009 Author Posted October 2, 2009 cheers guys, adding the dns record as suggested seems to have sped it up a fair bit...so many thanks.
Cools Posted October 2, 2009 Posted October 2, 2009 Can you add some sort of exclusion that would stop internal requests for the Moodle box going via ISA? Also, what web server software is Moodle running under? Replacing Apache with Lighttpd+Xcache got me a 200%+ speed increase (in terms of requests per second), for example. info here Nginx HTTP Server + PHP5 (With fast-cgi And xcache) On Ubuntu Feisty Fawn | HowtoForge - Linux Howtos and Tutorials 1
Ashm Posted October 2, 2009 Posted October 2, 2009 The only disadvantage with using Lighttpd is that you can't use NTLM single sign on as far as I know. Otherwise we'd be using it instead of Apache.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now