Yes, there are some processor-intensive tasks – most notably, OCR – in which one would see a significant performance gap between the lowest speed 1.4 GHz processor for the 11-inch MacBook Air, and the highest speed 2.13 GHz processor for the 13-inch MacBook Air. And there are other speed improvements for the newer i5 and i7 CPUs in current Macs compared to the older Core 2 Duo chips in the MacBook Airs.
But most of the operations one conducts with a DT Pro/Office database would be reasonably responsive on an 11-inch MacBook Air, so long as there is free RAM available for processing and Virtual Memory isn’t being heavily used. Apple’s Virtual Memory allows your Mac to continue memory-intensive procedures to completion even after the free physical RAM has been used up. This is done by swapping data back and forth between RAM and disk as the data is called for by the procedure. But read/write operations in RAM are orders of magnitude faster than read/write operations on a hard drive, so processing slows down, and the dreaded spinning ball will likely pop up. (The penalty is mitigated to a degree on the MacBook Air, because its solid state drive has faster read/write speeds than a typical hard drive.)
I’m a nut about demanding quick responsiveness from my DT Pro/Office databases. From 2005 to 2008 I ran them on a Mac with 2 GB RAM. From 2008 onwards the minimum RAM in my Macs has been 4 GB, and my iMac with i7 CPU has 8 GB RAM.
The approach I’ve used is to create topically designed databases that fit comfortably within the available free physical RAM, so that Virtual Memory rarely comes into play when I’m running them. My main database that I use for research and writing contains about 25,000 reference documents and about 5,000 of my notes and annotations about them, and is approaching 40 million total words. I’ve got a number of other databases for other topics, such as my financial information. I can open and close databases when I need to search across them or to work with a specific one. Obviously, I can have more databases open on my iMac with 8 GB RAM than on my laptop with 4 GB RAM, but any one of them will run very responsively on my laptop.
That’s why I expect to get quite reasonable performance with the new MacBook Air, which is to be delivered today with the 2.13 GHz CPU and 4 GB RAM.
Note that memory management on Macs, while good, isn’t completely efficient, so that data stored in RAM that is no longer needed will not be completely cleared, and will accumulate over time, reducing the amount of free physical RAM available for new tasks. So I monitor the amount of free RAM (Activity Monitor can do that). When I see that it’s getting low, perhaps after several days of intensively pounding my databases, I’ll quit and relaunch DT Pro Office, and eventually will restart the computer to clear everything out. If I see page outs starting to accumulate in Activity Monitor, I know that it’s time to do a restart.
So that’s how I keep my databases running at the maximum speed of which my Macs are capable. Cluster related data into databases that will fit in my available RAM, occasionally monitor the remaining free RAM, and restart when memory starts to get cluttered by remnants of unnecessary data in RAM.
I went for the 13-inch MacBook Air primarily because it offers more storage space than the smaller one. I’ve got a LOT of data among my databases that I’ll be carrying around, probably more than the average bear.