Jump to content

Recommended Posts

Posted

Hi guys,

 

Anyone else experiencing FOG running reeallllyyy slow on the GUI interface? Any ideas.

 

Running 0.29. Was fine before Summer and come to use it now and it's really frustrating.

 

Cheers,

 

Simon.

Posted
If you need to go through a proxy for internet access the interface will run slowly unless you've given the proxy details on the settings page.
  • 1 month later...
Posted

I think it is due to the new "Host is up" red/green lights that display beside each host name. Viewing the page source shows that jquery is loaded in the HTML HEAD section. Not sure if it was being loaded with 0.28, though I don't recall any javascript being used before 0.29.

 

I see the slowness in IE8, Chrome7, and Firefox3.6, especially listing hosts and editing hosts. The 0.29 web gui is much slower for me than 0.28 was. As much as I like the idea of the "Host is up" feature I'd rather have the quickness of the GUI back. I am on a gigabit LAN with ridiculously well-spec'ed server and web client, so it definitely appears to be a slowdown that was introduced into the latest web admin gui.

 

I would like to see an option to disable the javascript portions, assuming that is what is taking so long to load.

Posted
I found the same when listing hosts on 0.29, in FOG Settings try changing FOG_HOST_LOCKUP AND USE_ANIMATION_EFFECTS to 0 and you'll find it's back to being speedy :D
  • Thanks 3
  • 2 weeks later...
  • 1 month later...
Posted
Thanks, setting FOG_HOST_LOCKUP to 0 made all the difference!

 

I found that setting this breaks the host search feature - nothing happens as you type a hostname in the search box. With the setting back on the search works again.

  • 2 weeks later...
  • 2 weeks later...
Posted
Thanks Sy2K. That has worked.

 

@Chad Yep, found the same here. Something we can live with for now though.

 

A quick workaround if you want the search facility but don't want the host lookup is to remove the DNS server entries from your /etc/resolv.conf

I get all hosts instantly marked as "!" now but search works fine with FOG_HOST_LOCKUP still enabled.

 

I'll have a look at the code and see if I can see the issue when I get time, I've still to submit my WOL over subnets patch yet though.

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...