Monthly Archive for March, 2007

Swiftfox, why are’t we good nerds anymore?

So the past few weeks have seen me getting more and more frustrated with the performance lockups in Feisty. As a developer who’s been running it for several months now, I can say I’m very tolerant and never upset, just try my best to help, mostly by just finding my own solution. So cruft and buildup is inevitable, lots of random libraries compiled out of the packaging system to get something working last minute, and I know my kernel is a wreck, as its seen more than a few major upgrades. However, when I started to read benchmarks where Feisty was taking a significant beating in startup times, I started to get concerned. I agree with the reasoning that dropping the heavily optimized kernels was a good idea, I had stopped using them a bit before, due to my own stability problems.

Anyways, this prompted me to make good use of my 500 GB external drive, and I am backing up everything as I speak, then doing an all-out optimization of my system with no regards to consequence (just for some numbers/fun ;) ) and then installing the beta fresh (on a LVM’ed hard drive). I hope to have something of a comprehensive optimization guide for Ubuntu after this, but whats most likely going to happen is I get ansey for the new Feisty and LVM :)

However, as I started my quest for a meaner and leaner Gnome/Ubuntu harmony, I trudged through the debates on prelinks, preloads, and readaheads (do what you will, nothing fantastic either way for me). But the first thing that truly changed my day to day desktop experience and in an incredibly positive way was Swiftfox. Its nothing revolutionary in terms of ideas, its just done well. Swiftfox really isn’t even a separate distribution of Firefox, its almost the exact same code, just with highly optimized releases for each processor. My initial thoughts were that it was going to be worthless, and maybe for your processor, it is, but with the Core Duo, its a world of difference. At first I assumed it was placebo, or something else I had done, but when my benchmarks showed no real differences anywhere else, Swiftfox outpaced Firefox, by a lot.

Just for fun, I have a few links below for rough web rendering performance benchmarks, make of them what you will, but let me say, drop your composting manager first, both beryl and compiz hated me when I tried, its too many rapid refreshes.

http://scragz.com/tech/mozilla/test-rendering-time

http://celtickane.com/projects/jsspeed.php

http://www.24fun.com/downloadcenter/benchjs/benchjs.html

Feel free to share your times, either way, I’m interested to know if this was a ‘My Firefox was so messed up’ or if Swiftfox is truly that awesome nerd inside that drives the speed of software. ;)

Technorati Tags: , , , , , , ,

Powered by ScribeFire.

Bittorrent Software on Linux: Part 2

A follow up to my earlier post.

In my post last week I complained about how linux had no real torrent client that could go toe to toe with utorrent. Over the last week or so, I have been trying to follow up on all the awesome comments and suggestions that I got from readers. I found an answer.

Deluge is a Bittorrent client written in python and using libtorrent as a backend. Now, the release in Ubuntu Universe, and even its most recent 0.5 release were nothing to write home about, but the current SVN of Deluge shows serious promise. While I do *NOT* encourage users to try the SVN, as it is under active development (and I don’t want to force the project maintainer to answer a million questions about rapidly changing code) , I do feel that Deluge’s next release could match utorrent, or even surpass it! I found that while Deluge was taking a little longer to bootstrap less populated torrents, and the plugin/preference selection leaves something to be desired, Deluge is making huge progress in the speed area. Once I got torrents rolling, I found that Deluge was averaging about the same up and down as utorrent had been, and without the memory overhead of wine!

In short, I thank everyone for their awesome feedback, and thanks Deluge for stepping up and filling the niche for a full-featured and fast native linux client!

On a somewhat unrelated note, please consider filling out my survey on OpenID use if you haven’t already!

Lame Blog Linking Help

Miguel de Icaza has asked for some simple link help in getting Lame Blog some better Google results. I dunno if this helps at all, I don’t have a great Page Rank (I think its a 4 at the moment) so maybe its hurting, but the planets I get syndicated to do way better, so hopefully it helps.

New Theme, OpenID, and Sorry if I Spammed

Hey, so the 10 of you that actually visit my blog and don’t read it through a planet, you may have noticed me having some fun today. I decided that my blog was going to support OpenID, despite my hosting provider not having the needed math libraries, so my apologies if logins aren’t as speedy as you would like. However, dependencies and the like were not the hard part of the process at all, the OpenID Wordpress Plugin doesn’t really integrate into the site unless your running Kubrik or a derivative.

Luckily, there’s an easy enough solution, the OpenID API is pretty easy, and it didn’t take much to get everything (including Comments, and logging in via that link!) more or less running smoothly. On that note, don’t hesitate to nag, I hope its something people actually want to use. Its in that spirit that I have this little poll, no obligation, I was just thinking about pushing for Gnome to consider the MoinMoin plugin on live.gnome.org.

Ajax Polls and Planets do not like each other! Please participate in the poll here.

My last fun tidbit for the evening is actually really useful, if anyone runs a Wordpress blog, they know that its not the fastest or lightest thing in the world. But, most likely they have heard of wp-cache2, and have reached a comfortable compromise. One thing that really sucks about wp-cache2, is you can’t compress pages and use it, which means were missing out on the biggest web speedup there is. I realized this evening that you can totally utilize php’s native compression, and completely bypass the issue. If you add the following to your .htacces in the wordpress folder, your looking at a significant speedup, at least, I noticed one.

php_flag zlib.output_compression on
php_value zlib.output_compression_level 2

I believe the compression levels are 1-5, but don’t quote me, I’m using 2 for the moment, and I’m happy, I might do some more tweaking later though.

Its Always the Little Things

I love Linux, I use it all the time, my windows partition is constantly being ntfsresize’d to make room for some new (and completely pointless) project. So please believe me when I say, I mean no offense to anyone who has worked on a project I might cite here, its just me venting a general frustration.

Why is it that uTorrent is such a great bittorrent client? Even under wine, it outstrips every other client I have found for download and upload speeds, but whats more, its still running in a smaller memory footprint! Now, I’m not someone who claims that every line of open source code is holy, and that if code is developed openly it is by nature incredible, its just aggravating how often I find myself turning to wine.

Now, for some things (aka the DirectX unit in my game design class ;) )  you just know your going to use something, be it Vmware, qemu, wine, or (god forbid) actually booting into windows. but Bittorrent is ours. Its an open creation through and through, its open source, an open standard, and an important element of the open source communities infrastructure. In fact, the distribution of Linux ISO’s is one of the few mainstream legal uses….. *sigh* I know its a pointless rant, but wouldn’t it stand to reason that the open source world would hold the key to the fastest, lightest, and most reliable bittorrent client?

I don’t want to sound like I’m attacking the open source clients, they’re solid, generally reliable, and never a major pain to use, but no one really offers what utorrent does.

Its a silly and pointless ramble, and I’m open to thoughts, questions, or ideas, so fire away ;)

Oh, and one last thing, can I just give Wine some incredible, huge, and mad props for the past few months have been big, and the hardwork shows, many thanks.

Planet Beagle Random Icon Link Thinger

Hey, So I felt like giving Planet Beagle some random-junk-on-the-side-of-my-blog love, so this little guy was created, make of him what you will, but know I’m no artist. However, a small problem, we have no SVG’s or any other source-type format of the new Beagle Logo, we still ship the old one in our tarball, if someone knows where one is, I’d like to do some general random art/junk creation. ;)

Planet Beagle

So yeah, I know its a little big, feel free to do whatever, but I completely didn’t think about the whole saving as a small raster, can’t edit much thing… so just know I’m sorry, and feel free to improve or recreate as you see fit.

Code to use on your own page:

<a href="http://planetbeagle.org" title="Planet Beagle" target="_blank"><img src="http://kubasik.net/photos/beagle-planet.png" title="Planet Beagle" alt="Planet Beagle" />
</a>

p.s. If anyone knows what these are actually called, I would totally benefit from knowing there real name.

Google Docs as a Blog Editor

Google Docs as a Blog Editor

As a user of writely.com far before that whole Google purchase, I was tentative about the move, but also excited (as Google generally seems to have the whole Web-App thing down cold.) during the general crazy nature of school and a wireless card that had horrible linux support until 2.6.20 (many a thanks to the fellows over at the bcm43xx project ) a web based solution wasn’t really practical, but given a recent group project where collaboration was a big thing, I gave it another try, and as a collaborative outline/scratch sheet, it was fantastic. Given the scientific nature of the project, and the massive amount of math to be displayed/edited for the final report, OpenOffice.org had that honor, but Google Docs won some points with me for general usability.

After noticing the Collaborate button, next came Publish. The ability to post to a blog seemed pretty nifty, and Wordpress’ WYSIWYG editor constantly gives me headaches, as it never seems to display properly with my theme (maybe I just use a crappy theme, but I’ve shoved way to many of my own hacks in there, and its probably not gonna change super-soon). Recently Flock has been my blogger of choice given its other awesome blog-conducive features, and generally awesome layout, but its still based on Firefox 1.5, and as such suffers from a spell check that I have to run to use, which is a silly, but major pain for a horrid speller like me. I think a 2.0 based version is soon, but its enough for me to hold flock off as a primary browser, and as such, it loses potential as a blogging editor. Unfortunately pretty much every other open source blog editor is either lacking in features (like tagging/pingbacks/accurate rendering of HTML) or so buggy that its not worth the trouble.

So here I am, slamming out a quickie blog post in Google Docs, composition has gone great, its easy to use, surprisingly robust, especially in some areas (like key bindings) where I didn’t expect a webapp to do such a nice job. In addition, while I was setting up my blog, I learned that Google Docs supports categories (not the easiest system, as you do have to leave the editor to tag the document, but it can happen, so that’s cool.) So far my two main issues with most editors have been met with a simple grace I’ve almost come to expect from Google. Now the fun part, I’m going to post this to see how Google does with the formatting component, so if you see this, and their is nothing below, I’m just writing, give me a few minutes, and I’ll catch up.

Update:

Wow, not a half bad job! It seems to do fine, and supports my theme well (I guess the Planets are another test, but I’m not gonna wait for them :) ). All said and done, Google did a nice job it seems. I know I didn’t try anything wild, but here are two sweet screenshots, one in Google Docs, and one on my Blog, since it all seemed to go nicely.



So see for yourself. One thing I feel Google kinda screwed themselves up on, is that I was forced to upload these photos to Google, I gladly would have hosted them or pawned them off on Flickr, but Google had no (visible to me at least) way of doing that through the interface (which is kinda the point). So they just added some pain to their servers, and whats worse, I’m way to lazy to thumbnail my own screenshots. (sorry!) I always just take that small size from Flickr….

Anyways, formatting issues anywhere else, or generally noticed, please post a comment, I promise I listen, and to all 10 people who read this, I would prefer if you could actually read it without hurting yourself. ;)

Mirrors are Awesome

Ok, so as many of you know, I run Ubuntu on my laptop, and generally like to lend a helping hand wherever its appropriate when working on/with Ubuntu. With the latest release of herd-5, I realized the Feisty release is not far away. I happen to have a hosting plan with quite a bit of bandwidth that isn’t really used for much beyond this blog and a few of my own packages/sources. So, to lend as best a hand as I can for release time, I have decided to host an iso release mirror.

The actual mirror url is here.

I encourage anyone who is going to be downloading Feisty iso’s to try and use mirrors like mine (generally extremely low usage) to help us keep the master servers alive on release day. I expect my mirror will have the images within 35-45 minutes of release (if not before, maybe there’s some awesome way for those of us planning on mirroring to grab releases before the craze starts).

technorati tags:, ,

Blogged with Flock

General Beagle Busyness

Hey, so I’ve been pretty busy (again! *Shock* ) with school and haven’t had a ton of hacking time as of late. I’ve learned this means definatly pick jobs that don’t require a lot of follow up or that someone else is waiting on.

Anyways, I had some beagle-fun last night and was somewhat productive.

  1. I started a Launchpad Team and Branch to maintain our Ubuntu beagle packages. I think the trick here is going to be paying closer attention to Debian, as both an upstream developer and a 2nd tier packager, I always think I’m going to be on top of the Debian packaging solution/patches, but rarely ever am. So anyways, I’m hoping to parallel/stalk what they do so we can avoid more nasty merges right after Upstream Version Freezes are instated.
  2. Documentation! A long while back I started to fill out the automatically generated Monodocs for Beagles public API. While they’re still nowhere near done (API Docs are a royal pain to write, you feel so redundant), I have started to pick that up again, so should you want to write some bindings for BeagleClient, start working on Dashboard again, or even start another search interface, at some point and time, there should be some quasi-complete API coverage in addition to the Beagle Wiki.
    1. And just so everyone knows, its easy to help out! if you have monodoc installed, you have everything you need! There is another bzr branch just for the BeagleClient docs. If I made you a member of the “Beagle Packers” team, you can commit straight to the branch, just let me know you did and I’ll update it on my server. As for the actual editing, it couldn’t be easier:

monodoc –edit ./path/to/docs/dir/ and your editing!

p.s. More Documentation news, I updated my libbeagle docs that are online too.

Technorati Tags: , , , , ,