Using Firebug I did notice that there was a delay when our webclient couldn't load a stylesheet from static.opensuse.org. Just from load on opensuse's servers, shouldn't local instances of OBS point to their own statics subdomain. I guess this could be extended to putting all the branding stuff in an easily swappable subpackage of obs-server that obs-api then requires, like Requires: obs-branding. This would probably be more correct anyway since our local OBS isn't sponsored by OBS and the help links should really be pointed at our internal help docs so our internal users aren't swamping this mailing list with questions that only apply to our instance. If I figured out a way to pull out the branding so it's more configurable, would the community accept a patch to obs-server? That way any new branding wouldn't have to be extracted on each vendor drop. Sent from my iPod On Jul 11, 2009, at 1:01 PM, "Anas Nashif" <nashif@linux.intel.com> wrote:
one possible reason for slowness could be the fact that the webclient references static.opensuse.org for all kind of style sheets and image. If you are behind some proxy, sometimes this makes the webclient unusable. Solution is to change all those references to a local address.
Anas
On 10-Jul-09, at 3:28 AM, Luke Imhoff wrote:
We're running into issues with our local OBS instance in that it's running slowly. The web frontend is taking like 4 seconds to load some pages. I'd like to know how the public OBS is broken up as right now we have everything OBS related on one machine and I really have no idea how we can break up OBS to lower load. That is, which pieces can go on different machines and which need to be on the same machine. -- To unsubscribe, e-mail: opensuse-buildservice +unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org