Hello,
Sorry I don’t know which category this post belong to.
I found the forums of opensuse (https://forums.opensuse.org) is a bit slow to load, and also it is slow for https://software.opensuse.org to make search.
but https://forums.suse.com looks faster than opensuse’s forum. Can we improve it? and how can we do it?
I’m using Telekom with high bandwidth port in Germany. I don’t think it is internet problem.
Thank you 
Will move to Forums Feedback.
Thank you deano.
Yes,
For many weeks now I’ve seen numerous possible causes…
From about Thurs through Saturday and often through the entire weekend, I’ve seen likely work being done with the authentication provider, at one time changing the Domain name from microfocus (possibly replacing the entire authentication provider?) but now still using that domain name. If this is being done, I’d ask that changes be developed and tested to a mirror staging network first, and only when ready to apply to Production to lessen the disruption that is happening weekly and regularly. Designed properly, the mirror development network could even become part of a fault tolerant strategy to either temporarily support increased capacity or backup.
I also see latencies that look like they could be associated with some kind of proxy caching in front of the webserver farm which ordinarily should speed things up once pages have been accessed more than once. But, that first access is really, really slow when I’d normally expect only a few extra, maybe tens of seconds to load the cache. And if pages change then only part of the page might be cacheable… Someone who knows the proxy cache should be communicating with the Forum Development team either at SUSE or at the software’s authors (I think it’s still vBulletin?) to know how to write the software so that it’s compatible with how the web caching proxy works. Or, replace the proxy if it doesn’t work with the software. And of course every time systems are rebooted, the caches may have to be reloaded again.
If it’s not a web caching proxy issue, then it’s the webservers themselves or how they’re configured which are over-loaded.
In the past, I’ve seen signs that it’s a single webserver for all the Forums, if so then someone should be tasked to determine best way forward to expand capacity while also incorporating desirable features like fault tolerance.
In any case,
If there is regular work being done in these areas, they should be co-ordinated by someone… It makes no sense for multiple people to be tinkering on the things that might effect others blindly.
Hope that’s happening and not several people authorized to do things all own their own.
IMO and speculating,
TSU
thank you tsu.
People can tolerate slow authentication speed, after all it is only takes one time. But from my experience, the website is a bit slow even I do not login in to my account.
I wish all is well to my favorite OpenSUSE! And many thanks to all contributors!
Circumstantial evidence suggests that there is a web caching proxy in front of Forums website.
'Way back when,
For one company I worked for,
We wrote a small script that “warmed up” the website content whenever the system was rebooted and the cache needed to be repopulated. Difference is that we only had to warm up a few pages and not the literally hundreds or thousands of individual pages in just the English forums alone.
I’d still recommend though that if the system(s) is going to be rebooted often that someone should consider writing a script that walks through… say, all Forum threads within the past 12 hrs with a simple http request to populate the cache with what I assume would be the most current and accessed Forum threads.
The other approach might be to evaluate whether a web cache is even that useful for the Forums, evaluating how often a page is accessed (after the first time) and whether resources should be allocated to the webservers rather than web caching… that is, unless the web caching is also configured as security devices (blocking potentially malicious traffic).
But, in any case I think the most preferable solution is to set up a development and staging process that doesn’t touch Production unless and until final, fully validated and tested changes are ready to be deployed… Ie setting up a mirror of the authentication and deployed systems for experimentation.
Just throwing out ideas,
TSU