FreshPorts has a web page caching issue for all non-port commits. This also affects commits in the ports tree that do not touch a port. e.g. Mk, Tools, etc. I hope to fix it later this week. dev does not have this problem. beta & www do.
I think I’ve fixed a problem with caching of non-ports. I was looking for something to do tonight after I could not sleep. I found a old post about a this issue and figured I could fix it. The fix is in BETA. I’ll monitor it for a while before pushing it to production. Full …
Cydex mentioned to me today: dvl: /UPDATING and /MOVED don’t seem to be updating on FreshPorts My response, ever so witty: dvl: /UPDATING and /MOVED don’t seem to be updating on FreshPorts I started comparing the production website with the one I run at home. The UPDATING pages differed. So did the MOVED pages. I …
I have written much about caching. FreshPorts has over 500,000 pages. Only a handful of those pages are static, the rest are generated from the database. Sometimes it takes a while to generate that page. To reduce the load on the server and make the website snappier for the user, page contents are cached to …
I’ve managed to fix the caching problem previously mentioned. I think I solved it the night I wrote about it, but I’m only writing about it now. The code has been in BETA since then and has just moved into production. The log output now looks more like this: Observer has noticed that processing has …
I know we have a caching problem. I suspect I know the cause. The symptoms of the problem are: a commit has been processed by the system. the commit can be viewed via the URL /commit.php?message_id=MESSAGEID the commit can be seen via index.php or date.php the commit cannot be view on the port page I …
I ran some tests today. Without caching, I got 5.36 transactions per second (tps). If commit history is cached, I get 7.25 tps. What actually happens in a transaction isn’t relevent. What is important is that by caching I get 35% more transaction per second. That is, the system performance increase by 35%. That’s pretty …
In addition to the port history caching which I mentioned previously, I recently implemented some changes which will make it easier to cache yet more data. Specifically, the port details (e.g short description, long description). I’ve been playing with benchmarks/siege to see how many transactions per second I can put through my development server. Then …
Caching to disk, at least for ports, is now implemented. I didn’t plan to moved a new feature into production on the day before I leave for a conference, but it happened. If you notice that the website has not been updated after a port has been committed, please let me know. That will indicate …
Last week I took the car in for an oil change. I usually wait for the work to be done, and while waiting, I head over the road to a Perkins for some breakfast. While there, I usually do a bit of coding. It is actually a good environment for this. The place isn’t full …