Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Very slow performance. Numbers is pokey, that's for sure.

I'm mainly interested in using this thread to see how many others feel the same way; that Numbers is slow in general. At least on my machine it is. I get much better performance from the ancient MS Excel 2000 running in Windows XP via Parallels on the same machine. And XP is running in less than 400 megs of RAM!

I know it's a 1.0 release, but scrolling, opening .csv files, formatting multiple columns, all are slower than my old MS Excel. Given that Parallels is not multi-core aware, is virtualized, is running an 8 year old version of Excel, and is running in less than half the available RAM, I really expected Numbers running natively to make a better showing for itself.

iMac intel core duo 2.16 Ghz 1 meg of ram, Mac OS X (10.4.10)

Posted on Aug 8, 2007 10:44 AM

Reply
32 replies

Aug 8, 2007 10:57 AM in response to kevin spake

One thing I forgot to mention - it makes my entire computer slow. Well, when I am running Pages, Numbers, iTunes, Adium, and ms remote desktop beta 2, my computer acts more sluggish. I can run twice as many apps in parallels without it slowing down the whole system. I am just now starting to use the ms rdp 2 beta and iWork, so one of those is the culprit.

Aug 9, 2007 3:13 AM in response to kevin spake

It seems as if Apple never tested Numbers for use with "large" amounts of data.

The very first thing I tried to do was import a list of data (about 250 rows and 2-3 columns) to make a chart. Any change I made took 20-30 seconds if not minutes. Based on a hour's usage, Numbers 1.0 doesn't seem to be able to handle "serious" data use. Anything more than the 10-15 rows of data that Jobs demoed at the Apple Event or that are shown on those video tutorials.

Aug 9, 2007 9:06 AM in response to Ruudberg

While it is unreasonable to expect to pay $79 for an office suite that competes on every level with M$ Office, Numbers still does not make a good showing in several areas. It really should be called "Lists" because I think it probably does that beautifully.

On the other hand, Apple has a history of putting out fairly weak 1.0 software and then making some pretty quick improvements. Let's hope Numbers gets fixed quickly. I was hoping that iWork would allow me to use native Apple apps and stop relying on Parallels so much.

Aug 10, 2007 4:34 AM in response to kevin spake

I would agree that Apple is good about launching something which is a bit pre-mature. In many ways I prefer this. I would rather get something now that provides a sense of direct rather than wait for something that is perfect months or a year later.

On a related note it is better for Apple to release early and get feedback. I saw a number of projects where the vendor did not have the same sense of direction as the customers. An early release let the customers provide feedback which caused major changes in the product on subsequent releases.

I do not have iWorks 08 yet but I will be buying. I have enjoyed using Pages and Keynote so I expect more of the same plus the addition of Numbers.

John Corey

Aug 10, 2007 6:05 AM in response to Ruudberg

Yes. Comparisons to Excel are not warranted, for better or worse. It does many many things very nicely as a spreadsheet app. It just so happens that one of the main things I would need it for is to work with "meaningful" amounts of data, in other words more than 20 rows of numbers (250-2500). I'm sure a version 1.0.1 or perhaps 2.0 will improve performance so that it doesn't ground to hault.

Aug 10, 2007 6:34 AM in response to kevin spake

*On the other hand, Apple has a history of putting out fairly weak 1.0 software and then making some pretty quick improvements.*
I've been saying this for quite a few years. It's almost as if Apple throws out a little program saying, "Let's see what they make of this." Then the team sits back, watches to see how we use it, and then brings out the next version with features to help us use it that way.

Aug 10, 2007 9:54 AM in response to kevin spake

Forget the unfair comparisons to excel, numbers can't even keep up with AppleWorks!

I have a spreadsheet in Apple Works that I use to track revenue and profit for my business. I enter two numbers per day: Total Sales and Total Profit. There are 6 calculation columns that display 7 and 28 day running averages for sales, profit and margin each day. The spread sheet is about 1400 rows (one row per day). No special formatting, no formulas more complicated than if(), sum() and average().

In Appleworks:
Data entry: instant - as fast as I can type.
Create a line chart on 6 columns and 1400 rows: 5 seconds
Memory usage: 11 MB

In Numbers:
Data entry time: Spinning beachball for ~10 minutes after each keypress (yes, REALLY)
Create chart: Unknown, maybe not possible. (Still waiting after 1 hour of spinning beach ball and 100% processor usage)
Memory usage: 1009MB (yes, ONE GIG), plus 2GB VM file (!!!).

I mean, how sad - ONE HUNDRED times more memory usage and over ONE HUNDRED tomes SLOWER. Absolutely terrible. If I were the engineer on this project I would be absolutely ashamed of the performance.

Aug 10, 2007 2:32 PM in response to dwb

I've been saying this for quite a few years. It's almost as if Apple throws out a little program saying, "Let's see what they make of this." Then the team sits back, watches to see how we use it, and then brings out the next version with features to help us use it that way.


Actually, if the development team really listens and delivers the customer requested features, this is the best development process. Much better than developing it internally for years and trying to sell an unproven software with a feature set that might not meet customer's demands.

The incremental software process is like this:

* Step 1: develop a useful product. It might be less than perfect and have less than all thinkable features.
* Step 2: publish it as early as possible
* Step 3: collect user feedback
* Step 4: improve the product based on user feedback
* Step 5: Go To Step 2

If the interval is short enough (a month, three months, ...), then this incremental process quickly leads to a usable software with the features customers really need.

Aug 11, 2007 12:09 AM in response to Rob Stevenson

To follow up on my own comment - I did a little more playing around and discovered that most of the performance hit comes when using currency formatting on cells.

Changing 1400 cells from "Auto" formatting to "Fixed" formatting with 2 decimal places takes 5 seconds (slow but bearable). Changing the same 1400 cells to "Currency" format takes over three minutes of spinning beachball.

I'm not sure why the addition of a dollar sign to the display would make such a big difference, but if I set all the columns in my spreadsheet to currency formatting the entire program is completely grinds to a halt. If I use fixed formatting it is still slow but at least does not take 5 minutes to change one cell.

Very slow performance. Numbers is pokey, that's for sure.

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.