Archive for the ‘Mac OS/X’ Category
And I have a “solution.”
So what is the situation? Consider an actual page from a webapp I’m developing. In FireFox the page loads and renders in something around 0.6 seconds. Safari loads and renders the same page in 12 seconds. This is not a contrived example.
What’s involved on the page? It displays summary information about all of the users of the webapp. The test data has 119 users. It uses [Blueprint](http://www.blueprintcss.org/) and the jQuery plugin [ListNav](http://www.ihwy.com/labs/jquery-listnav-plugin.aspx). I recommend them both, very nice. [ListNav](http://www.ihwy.com/labs/jquery-listnav-plugin.aspx) (check out the [demo pages](http://www.ihwy.com/labs/Demos/Current/jquery-listnav-plugin.aspx)) allows for easy navigation through a long list. [Blueprint](http://www.blueprintcss.org/) is a CSS framework for laying out a page using a grid (check it out, it has [demos](http://www.blueprintcss.org/tests/parts/sample.html) too), handles typography, and generally helps you make a page look decent. Blueprint works with <div>s, and ListNav wraps them up in <ul>s. Each user is represented by five <div>s within a <ul>.
On Safari, by changing the number of <div>s for each user I get:
|user < div>s||render time|
To cut it short, if I remove the link tag to the Blueprint screen.css file in the header, the page renders almost instantly, even with 8 divs — but it looks like crap. There are a lot of things that are not the problem (I was “busy”, let’s say), and I don’t really want to go into it.
This is (obviously) in the jQuery document ready function.
And it worked! In Safari. Not so well in FireFox. Sigh. In FireFox, this caused a rendering effect: the unstyled content would flash on the screen before being being styled. So, back to the webapp, and check the user agent, and only do this trick for Safari. Well, hold on. It is actually any AppleWebKit based user agent — OmniWeb screws up too. There’s probably others. Anyway, about 0.3s in Safari, obviously no change in FireFox, and I’m happy enough for now.
It all came down to a single link element in the page’s header.
Well then, fix it once and for all.
sudo mkdir /System/Library/CoreServices/JUNK sudo mv /System/Library/CoreServices/Front\ Row.app /System/Library/CoreServices/JUNK
or, if you are really in a state:
sudo rm /System/Library/CoreServices/Front\ Row.app
Then kill the already running Font Row.app process.
Gone! For good!
What a relief!
Why you ask? Well, for some reason Front Row keeps getting control of my machine. I don’t know why. But it is very distracting when it happens in the middle of something… wait for the fancy animation, wait for a couple seconds, hit escape or command-esc a couple of times (and if that doesn’t work, put the machine to sleep and wake it up, then try the escape, repeat as needed).
UPDATE: now we have vacuum mail
So the trick I posted 13 months ago didn’t work for me, though it did for some people.
Here is one that actually does work: A faster way to speed up Mail.app from Hawk Wings.
First off, it is trivial, run this after backing up…
sqlite3 "~/Library/Mail/Envelope Index" vacuum;
from a command line in OS X.
It reduced the sqlite3 DB from 50,760kb to 47,976kb which isn’t a lot, but then that isn’t the point is it?
What it did do was an almost magic speedup of Mail.app’s operation. Opening my inbox used to take 10-15 seconds the first time and about 5 seconds after that. Downloading email took about 1-3 seconds per message. I open my inbox in less than 2 seconds the first time and pretty much instantly after than, I can download email at rate of about 3 messages per second (that’s almost 10x faster).
It is like a new application.
I think I’ve solved my problem :-)
The one-minute UPDATE: and search is actually usable… ah, so this is why people keep saying how great and fast Mail.app searching is….
Once again, pleased that I don’t use windows any more.
Apple’s DRM imposed upon music downloaded from the iTunes store limits the music to playback on five different machines. I have two where I want the music authorised. But recently my PowerBook melted into a puddle of slag, the temporary replacement machine is no longer available to me and I didn’t think to deauthorise it, the new MacBook I purchased to replace the PowerBook went walkies, and the newer new MacBook I purchased is now humming along just fine. Trouble is, I hit my five machine limit on the DRM.
Well, it turns out that once the fifth machine is authorised, a new button appears on your iTunes store account home page “Deauthorize All” — it is not there until the fifth authorisation. If you click that button then all five machines will be deauthorised, and you can then re-authorise the machines that should be.
I don’t like this DRM stuff, for a lot of reasons. At least this relieves one worry.
UPDATE: so can I use this to maybe track down whoever it was that took my last MacBook? Anyone know?
Discusses a couple tools that allow you to monitor filesystem events in OS X. It uses the mechanism underlying Spotlight, not Spotlight itself.
This is kind of cool. It lets you browse Ruby RDoc files in a OS X Dashboard widget.