December 2008 - openSUSE Web - openSUSE Mailing Lists

[opensuse-web] Re: [opensuse-wiki] Several fixes for software.opensuse.org/expert.html
by Robert Lihm 24 Jan '09

24 Jan '09

Hello Christin, FYI: We have a new mailinglist for topics about www.opensuse.org. the wiki ml should stay for wiki thinks. On opensuse-web(a)opensuse.org you can reach all people who work on the openSUSE.org pages. So, if you want to contribute to the pages, please register on this mailing list (opensuse-web(a)opensuse.org => http://en.opensuse.org/Communicate/Mailinglists) . On 21.12.2008, at 15:53, Christian Boltz wrote: > Hello, > > on Sonntag, 21. Dezember 2008, Christian Boltz wrote: >> BTW: Are the software.o.o pages in some SVN? I couldn't find them on >> https://forgesvn1.novell.com/svn/opensuse/trunk/infrastructure/ ... > > I got a reply off-list and was pointed to > https://forgesvn1.novell.com/svn/opensuse/trunk/buildservice/src/software > (and also got an offer for SVN write access) > > The files are somewhat hidden, but grep helped to find them ;-) > software.o.o-expert.html -> public/expert.html > software.o.o-index.rhtml -> app/views/layouts/application_no_js.rhtml > software.o.o-index-unused.rhtml -> app/views/layouts/application.rhtml > (the application*.rhtml are nearly identical - I have no idea why both > files are needed) > > I just commited the fixes (r5996 for expert.html und r5967 > for application*.rhtml). The remaining part for whoever has > permissions > to "svn up" software.o.o is: proofread my changes and run svn up ;-) > (thanks to help.o.o, I already have write permissions *g*) > I take a look on your changes when am back in CW 1 2009. I can deploy them as well. Thank you for your engagement! >> BTW2: It would be a good idea to move the table to a separate file >> that is included by the <noscript> area and expert.html. This would >> save duplicate work and also ensures both pages share the same >> bugs^Wcontent ;-) > Yep, this is on the todo list. > I still think so. Some more openSUSE-like look for expert.html would > also be nice. > yep. Work in progress. Wish you all a the best for 2009! Cheers Robert > > Regards, > > Christian Boltz > -- > [Passwörter] Ich suche nach einem Mittelweg zwischen maximaler > Sicherheit und Zumutbarkeit für den Benutzer (ein Pferd mit Hufen, > dem unsere Admin-Tastaturen viel zu klein sind :-)). > [Manfred Rebentisch in suse-linux] > -- > To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org > For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org > --- Robert Lihm, Webdesigner - Build Service Team SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg Tel: +49-911-74053-0 - rlihm(a)suse.de ____________________________________________________________ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ____________________________________________________________ SUSE - a Novell business -- To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-web+help(a)opensuse.org

3 6

[opensuse-web] frontpage uses static.opensuse.org in SVN
by Andreas Demmer 20 Jan '09

20 Jan '09

Hi, I changed all stylesheet/javascript /image links of the openSUSE frontpage. They now point hard-coded to frontpage SVN checkout on static.opensuse.org This reduces the server load since static.opensuse.org is highly optimized to deliver static content. The code is now in SVN but not deployed on the live server yet. Reviews of my changes are highly welcome. Greets, Andreas -- Skype: andreas.demmer ICQ: 103 924 771 http://www.andreas-demmer.de

4 16

[opensuse-web] 11.1 release announcements in SVN
by Andreas Demmer 18 Dec '08

18 Dec '08

Hi, I just added the 11.1 release announcements in SVN trunk, so we are ready to rumble in T-22. I'll notify Mike Cronquist to "svn update" www.opensuse.org and static.opensuse.org on release time. Greets, Andreas -- Skype: andreas.demmer ICQ: 103 924 771 http://www.andreas-demmer.de

3 3

[opensuse-web] new frontpage screenshots in SVN
by Andreas Demmer 16 Dec '08

16 Dec '08

Hi, I've updated the frontpage screenshot slider and committed the changes into SVN. Now all screenshots are taken from openSUSE 11.1 I'll ask Zonker to write a short release statement, which I will add to the "What's hot" section of the frontpage, in both English and German. After the statement is in SVN, I will notify this mailing list. After this, we're ready to rumble. Means: On thursday, we can "SVN up" www.opensuse.org and static.opensuse.org/hosts/www.o.o to advertise a shiny, new openSUSE version! :-) Greets, Andreas -- Skype: andreas.demmer ICQ: 103 924 771 http://www.andreas-demmer.de

1 0

[opensuse-web] [HOTWO] create a local test setup for static.opensuse.org
by Andreas Demmer 16 Dec '08

16 Dec '08

Hi, I just have set up a local test environment for static.opensuse.org. I wanted to test, that new static content is really loaded from static.opensuse.org without having to deploy the new content on static.opensuse.org. It allows working with only one local checkout which simulates both checkouts on www.opensuse.org and static.opensuse.org Since this may be a common task for openSUSE web developers, I wrote this mini-howto: 1. Add static.opensuse.org to /etc/hostnames as a new alias for localhost: 127.0.0.1 localhost static.opensuse.org Ping static.opensuse.org to verify that 127.0.0.1 is returned 2. Create a new Apache vhost that listens on static.opensuse.org: <VirtualHost *:80> ServerName static.opensuse.org DocumentRoot /srv/www/vhosts/opensuse.org </VirtualHost> Make sure, that the DocumentRoot points to your local website files! 3. Add a RewriteRule if needed. In my case, the images which were available on www.opensuse.org/images now reside under static.opensuse.org/hosts/www.o.o/images Since I wanted to use ONE checkout for both www.opensuse.org AND static.opensuse.org on my machine, I needed to make sure that Apache ignores the deeper path information (/hosts/www.o.o). Therefore, I added a RewriteRule to the vhost: RewriteEngine On RewriteRule ^/hosts/www.o.o/(.*) /$1 [L] 4. Restart the Apache webserver and you're done! Your local machine now listens on static.opensuse.org and your Apache rewrites all requests for /hosts/www.o.o/any_file directly to /any_file. I thought this setup could be as useful for you as it is for me. Remember to deactivate the vhost when you are currently not developing, since any other content from static.opensuse.org won't load! If you encounter any difficulties, let me know. I see if I can help. Greets, Andreas -- Skype: andreas.demmer ICQ: 103 924 771 http://www.andreas-demmer.de

1 0

Re: [opensuse-web] frontpage news reverted back to ancient stuff
by Andreas Demmer 15 Dec '08

15 Dec '08

Andreas Demmer wrote: > > Thx! Did you use SVN or the WYSIWYG editor? If you used the editor, > > I will > > commit your changes into SVN. Robert Lihm wrote: > I used the WYSIWYG. I made a german translation as well and committed both into SVN. Greets, Andreas -- Skype: andreas.demmer ICQ: 103 924 771 http://www.andreas-demmer.de

1 0

[opensuse-web] frontpage news reverted back to ancient stuff
by Stephan Binner 15 Dec '08

15 Dec '08

Hello, for the last two(?) days the news section of www.opensuse.org advertized the upcoming 11.1 release (including "donwload" typo). Today it shows again the old "Website redesigned during the Hack Week III" news. What's happening? Bye, Steve -- To unsubscribe, e-mail: opensuse-web+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-web+help(a)opensuse.org

4 8

[opensuse-web] Myths and facts / the bitter truth of latencies
by Peter Poeml 11 Dec '08

11 Dec '08

Hi, I want to share some findings from the www.opensuse.org / wiki and iChain setup. Especially, I wanted to find out some things about iChain which served mainly as a black box for me so far ;-) # telnet en.opensuse.org 80 GET /skins/opensuse/css/local/wiki.css HTTP/1.1 Host: en.opensuse.org Connection: keep-alive [...] Connection closed by foreign host. # => iChain doesn't use Keepalive to clients. Asking Matt about it, he said it is a global setting that had to be disabled for one of the 35 web sites hosted through iChain. However, he thought it might have been do to some problem that no longer exists, and he wanted to do testing and possibly reenable it. => UPDATE from last night: iChain now *does* use Keepalive to clients. Matt could switch them on, and it doubles the request throughput. Cool! Looking at Expire headers, and playing with forced reloads, iChain clearly caches, and does this correctly. The requests served by cache hits correctly never turn up on the backend server, so they are effectively offloaded. However only some parts of the web site sets Expires headers. And the Expires headers that are set are much too short. => iChain caches. => Expires headers are missing. (we need to add them at the web server.) Playing with requests on wiki pages, I initially thought iChain also would compress (gzip content encoding). Matt didn't know about it either ;) and it turns out that the wiki does this. However, there are two problems with that: It is a little inconsistent, because it only occurs for some Accept encoding headers or user agents. root@doozer ~ # curl -sv -o /dev/null 'http://en.opensuse.org/Mirror_Infrastructure' 2>&1 | grep Enc < Vary: Accept-Encoding,Cookie root@doozer ~ # curl -sv -o /dev/null -H "Accept-Encoding: gzip,deflate" 'http://en.opensuse.org/Mirror_Infrastructure' 2>&1 | grep Enc > Accept-Encoding: gzip,deflate < Vary: Accept-Encoding,Cookie < Content-Encoding: gzip => iChain doesn't compress, the wiki does, but Apache doesn't. The front page should *definitely* be served compressed, in the future. Possibly, the PHP/zlib compression can just be replaced by Apache-wide compression (and caching). The (www.o.o) web server is pretty fast for many things. 50 r/s for a PHP script (typical speed), thousands of r/s for static stuff. => web server is fast. (I didn't look much at the wiki yet. I didn't look for hot spots.) Through iChain, the speed is retained. With iChain's caching it actually increases a little. On the local network, 4000-6000 r/s are possible through iChain. => iChain can be very fast. HOWEVER, real-life performance for a web client sucks, from Europe. 2 (two!) requests/s is what I get from Germany. (UPDATE from last night: 8 r/s, with Keepalive and three further machines.) The other direction works significantly better. software.o.o or static.o.o deliver 25 r/s to an US client without keepalive. 50 r/s with keepalive. Thus, Internet is 10x faster when the server is in Europe. These numbers are reproducible and not susceptible to circadian variation. In addition, from a different US server, I can pull 5x as many requests to Europe as from iChain. Enter curl -I http://www.opensuse.org/ http://www.opensuse.org/en/ (as an Europaean...) and watch the *huge* latency between the two requests. Note that it doesn't matter if a request is tiny or "only" a if-modified-since request, as the latency is the same. => ? what is the conclusion... iChain is slow? No explanation for this. TCP/IP stack of Netware is not good for WANs? General conclusion: => overseas Internet is slow for web serving in general. It has a big pipe but large buffers suffers high latencies. => It would be much better to run a server locally at every continent. Anyway, regarding 11.1 release we can do quite some things still; and also, the last nights improvements were really significant. It is unclear whether the additional servers helped with that, because something still looks like some weird bottleneck around iChain, but we definitely have a quadrupled request throughput since last night, even though Keepalives only account for half of the improvement, and we don't know what caused the rest. Peter -- Contact: admin(a)opensuse.org (a.k.a. ftpadmin(a)suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development

1 0

[opensuse-web] www.opensuse.org todo for 11.1 release
by Peter Poeml 11 Dec '08

11 Dec '08

Hi, I have the following on the todo list for the release, more or less in order of priority: a) Expires for the front page (missing so far) b) change links to referenced files to static.o.o (Andreas and Robert are working on that) c) use type-map instead of index.php to choose language variant, d) switch off ETags, which will be useless as long as there are multiple machines, and hurt browser caching I have the following thing which I regard as nothing more than optional, because I don't think we have enough time for it until next week. e) use gzip encoding for the front page stuff, with caching so that it doesn't absorb CPU. After the release, Darix will want to experiment with a PHP bytecode cache, which could give a good boost to PHP, provided it runs stable. It needs careful testing I guess and is something to play with after the release. Having additional machines could help with deploying that. All the above are just my optimization plans, it doesn't encompass other stuff, as enabling editing the front page news, and whatever else needs to be done :-) Peter -- Contact: admin(a)opensuse.org (a.k.a. ftpadmin(a)suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development

2 1

[opensuse-web] static.opensuse.org and what it's good for
by Peter Poeml 10 Dec '08

10 Dec '08

Hi, this is to let you know that static.opensuse.org, which has been existed for about 9 months, is now properly set up on a separate host which is optimized to handle static small requests. It does use transparent gzip content encoding and a short keepalive timeout. And it sends useful Expire times in the headers so that the stuff can be cached for a while (and not revalidated too often). It can effectively offload other servers, when they link to it, instead of delivering stuff themselves, like CSS files, images, javascript. It is worth taken into account that a typical browser is said to open two parallel connections per Host(name), so it is useful as such to link to different servers instead of just one, to increase parallelity of things downloaded by the browser. If you consider that a typical website has 30-50 included objects, it is useful to *save as many requests as possible*. This should be the highest priority for a good user experience. Keepalive is important to keep the transfer smooth and avoid additional, unnecessary roundtrip times for new connections - because latency is the worst enimy in our today's high speed networks. A roundtrip between Europe and the US can take between .2 and 0.5 seconds. Keepalives help avoiding more latency induced pauses than necessary. For Keepalives to be enabled on a high traffic server, it is needed that it is fast and lean enough so the slots occupied by open (but unused connections) are not too expensive - which is typically the case on a preforked, PHP-bloated seb server. The www.opensuse.org/*.opensuse.org sites hosted in Provo don't use Keepalive at this time, so it comes as a big advantage that static.o.o uses it. In addition, it is much faster to reach from the US, than vice versa (I may write a further mail about that later). static.o.o has a checkout of https://forgesvn1.novell.com/svn/opensuse/trunk/infrastructure and it would be cool if all of you would look into possibilities to link to static.o.o where possible. This should increase performance, and at the same time, it should make some things easier, because we can update and maintain some things in a common place. There's also quite some potential for cleanup and simplification I guess. The clumsy svn externals in the subdirectories of the tree are probably not needed anymore and a simple symlink can suffice. Sites that use static.o.o already: forums.o.o software.o.o build.o.o users.o.o (?) Sites that don't: news.o.o www.o.o / *.o.o (the wiki) lizard.o.o zonker.o.o ichain login page Peter -- Contact: admin(a)opensuse.org (a.k.a. ftpadmin(a)suse.com) #opensuse-mirrors on freenode.net Info: http://en.opensuse.org/Mirror_Infrastructure SUSE LINUX Products GmbH Research & Development

1 0