Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

Ticket #676 (new task)

Opened 16 years ago

Last modified 16 years ago

Caching proxy

Reported by: mrenzmann Assigned to: mrenzmann
Priority: minor Milestone:
Component: website Version:
Keywords: Cc:
Patch is attached: 0 Pending:


Most of the content on (at least the part that's served by Trac) is not very dynamic. Some parts, on the other hand, are very CPU intense when being rendered (for example the changeset viewer for svn commits with a new HAL release).

For now the few CPU-intense changeset pages are redirected to static snapshots, reducing the load of the server and getting rid of the former "changeset too big" page that was displayed for them before. However, it might be worth to see if Squid or some other caching proxy could reduce the server load more.

This should be tested on the new server during the preparation of the move.

Change History

06/08/06 16:19:00 changed by nuclearcat

Maybe good idea just to modify a code, and give a link to customer changeset_snapshot.html sure it must have correct Cache-control and etc. headers, so it will not stay forever in viewer cache.

and update this static page by cron hourly let's say (time window you must know better:) )

06/08/06 16:25:28 changed by mrenzmann

Given that the last-modified headers are handled correctly on both, Trac/Apache and the proxy that should work as well, without relying on a fixed update interval. In theory, at least :)

06/08/06 16:49:26 changed by nuclearcat

Ok not fixed, you can update page exactly, when changes done on changeset. But on my opinion, squid is too heavy and complicated for such tasks. There is modules even for apache available, and + there is special acceleration proxy nginx, developed for such things.