OpenOffice Bloated?
cygnusx writes "ZDNet's George Ou has been writing a series of posts about Open Office bloat. Includes some interesting system usage comparisons" From the article: "Even when dealing with what is essentially the same data, OpenOffice Calc uses up 211 MBs of private unsharable memory while Excel uses up 34 MBs of private unsharable memory. The fact that OpenOffice.org Calc takes about 100 times the CPU time explains the kind of drastic results we were getting where Excel could open a file in 2 seconds while Calc would take almost 3 minutes. Most of that massive speed difference is due to XML being very processor intensive, but Microsoft still handles its own XML files about 7 times faster than OpenOffice.org handles OpenDocument ODS format and uses far less memory than OpenOffice.org."
I seriously doubt that. I was working with files similar in size to the ones discussed in the article just last night, and I got completely opposite results. OO.org took half the time to load that Excel did and took up just over half the space for the files. I really don't know where they get these numbers. Probably a biased test with fundamentally different data. I hate trying new software that does the same thing, and I am by no means tech-savvy, but even I can see that OO.org runs laps around any MS product for my uses. I swear, this must be someone shilling for Microsoft.
Rank my idea: http://www.sinceslicedbread.com/node/531
So if you can do worse, your software is considered mega-bloated.
Java.
When attempting to replicate one of the biggest bloatware software packages out there, that they make a version even bigger and bloatier!
Thalasar
Consider that Intel owns a big chunk of CNET and then you see a possible conflict of interest brewing over an article possibly designed to sink Open Office. Now consider the author, George Ou, who has also posted such titles as, Is the Honeymoon with Firefox Over?
Seeing a bit of a pattern forming.
The dangers of knowledge trigger emotional distress in human beings.
Talk about stating the obvious... have you never tried to compile an app written by Sun before? The bloat just slaps you in the face repeatedly until you submit
And from what I have seen it does run a bit slow. If you try to open a file from the web might as well go get a drink. Maybe its just my computer?
I Pong
How much of this slowness is the application's fault vs. this being a giant Java app running in a JRE? AFAIK, MS Office 2003 is still a suite of (mostly) C++ applications, and isn't running in .NET yet.
John
Could it be the GUI? Excel uses native widgets and I'm sure is heavily optimized towards MFC (after all, its their API!). I don't think OO has that luxury. I doubt thats the entire issue but it could partially explain it.
Excel also crashes faster than Calc! *ducks*
Perhaps the reason that OO uses more private memory than does MS Office is that MS Office links to all the MS dll files, while OO bundles its own internal libraries with it?
And from article/blog/whatever: "Now to be fair, OpenOffice.org is free and is cross platform, but does this really matter to the 90% of the users in the world who only use Windows?"
If it's legally free to use and does the same task, why wouldn't 90% of the users in the world who only use Windows *not* care? People always look for what's cheaper, sometimes even if it's not better (note how MS became the company it is today...)
Most of the bloat I see results from kludging together work from multiple sources that are not communicating well. Can't they solve this by switching to a faster parser? Or is the format itself flawed? So many questions, this doesn't bode well. Speaking of bloat, why do linux distros come on 5 CDs with multiple versions of every possible thing. Have options is nice, but the fragmentation is getting out of head.
It's interesting today to see the bloat and memory hog complaints leveled against the non-Microsoft product while showing MS' version as lean and mean.
I can't defend the numbers, they do look huge, but we're seeing about one or two articles a week in the trade rags about the latest memory, cpu, cache, etc. advances. Technological advances render all but the most dramatic processing demands almost moot.
In the numbers and benchmarks from this article, unfortunately, this is one of the more dramatic instances. I'm always willing to wait a little more for opening an application, or a file if other factors offset. In this case, free vs. whatever Office goes for now, typically is enough of an offset, but maybe not so for a large company where that extra "time" and computer resources add up big, and the pricing is likely to be more disounted for volume licensing.
Interesting numbers on the two different speeds on processing XML. Does anyone know or conjecture the difference in the true internal XML data for the comparison? I thought OpenOffice was the more pure in the sense that it is true human readable data in the XML while Microsoft's format is more of an envelope architecture for binary proprietary Office payloads. And, I wonder what the specifics in this test were around that.
Bottom line for me: I'm still going with OpenOffice, I've been a fan for years.
[see post title]
- vi is a bloated version of ex
- EMACS stands for Eight Megabytes and Continually Swapping
- Sometimes I just telnet to port 80 instead of using a browser
I have compiled OpenOffice from scratch... took a while!sounds like an abuse of XML, which should be used for data transport and not really data storage, for that there's binary.
I don't use Windows and haven't since '98. At one point, I ran Linux, but kept a dual boot system with Windows, just for opening complex Word documents. Then, I started using Crossover and that saved me a lot of time and I eventually wiped Windows off my box for good.
Now I got into OS X, and I run MS Office on it. I must say though, without bias, that MS Office has to be their greatest product. It just works and I haven't ever had any issues with it at all. It is fast, user friendly, stable and usable. Let's face it: when coders code a word processor they will always look at MS Office for implementation ideas. On the Powerbook, MS Office just flies.
A few weeks ago, I tried to run Openoffice on my Debian box, and there was a huge performance decrease, when compared to running MS Office. It was certainly noticeable. It took a while for a document to open up.
Though, Office has been around for a long time and Openoffice hasn't, so I'm sure there will be lots of features and performance gains in the coming years for the latter. I'm definitely going to keep an eye on Openoffice.
On its face MS Office does not handle OpenDocument format so theother claism are entirely suspect.. Do anly /. contribs actually read what they submit?
Fred Grott(aka shareme) http://mobilebytes.wordpress.com
I get the exact opposite results for Excel and OpenOffice Calc: Excel takes forever to load, doesn't share memory, etc, and Calc is a lot faster/leaner.
Then again, I'm running Excel in Crossover Office; all those Windows libraries aren't "preloaded" for me. Maybe that's why XP and Vista have such large system requirements?
...but I am sure that if there is any truth to this, it will be addressed and corrected in a fairly short time. I believe it's really as simple as that.
I think it would be really nice of the people producing the article to make the sample data available to the rest of us to see the results for ourselves.
I'm not surprised, I heard MS put secret anti open office code in their latest security updates to fool the sheep into using their stuff because it 'appears' superior in every way. To that I say HA! You've not fooled me!
Just go ahead and admit it, they both suck for different reasons. We need a third player.
This is total garbage. I have been using OO 2.0 at home since it was released and I have noticed no lag compared to Office which I have to use at work. I do not have quantitative numbers to present, but I can certainly attest anecdotally that this blogger is flat-out wrong. I notice no appreciable speed difference between the two suites while processing the same files. (The machines are roughly equivalent at home and office)
I recently purchased an iBook G4 which came with a trial edition of Office.Mac (or whatever it's called). I used it for the 45 days of the trial and then switched to "OpenOffice.org for the Mac," otherwise known as NeoOfficeJ. The only thing I've noticed thusfar is that Neo takes about 1.5 times longer to run initially, and it seems to take longer to save files. Other than that I really haven't noticed any other differences in performance.
Americans LOVE bloat. All you-can-eat restaurants. Trucks with HEMIs and lift-kits only driven on pavement. Giant houses with even larger pole barns. You'd think it'd be a little more popular.
If someone says he and his monkey have nothing to hide, they almost certainly do.
Yes, potentially if they are parsing the XML into a full DOM tree, this could potentially take MASSIVE ammounts of memory. If you read up on the DOM parser for java. There are clearly many benifits of parsing an xml document into a DOM tree structurally and whatnot, but practically, at this point, if your document is large its just not viable memory wise. I don't know if this is what OO does, but its just a possible explaination.
Hypocrite - show some repeatable results, don't just talk out of your ass!
These articles are complete garbage. No mention of methodology is made. What files were loaded, what conditions were they loaded under. Was it the same machine, or a very similar machine. What distro, what JVM, and on, and on, and on. Sounds like another MS shill to me.
He is already anti-Open Document http://government.zdnet.com/?p=1723 and heavly pro-Microsoft http://blogs.zdnet.com/Ou/ so this is not unexpected.
The fact that people are carping about efficiency means that it largely has what they need.
There is a fix available here if you run Windows:
http://www.microsoft.com/office/
For those running Linux, you'll also need this:
http://www.codeweavers.com/products/
I'm not sure. I know I rarely use anything except writer, so maybe having a writer lite edition as well as the whole suite.
"Persistence is annoying success." - ghee22 11:28:1999 - 10:53:PM
There is question what exactly these results mean. Pure memory usage is very hard to compare because Microsoft Office is based on their own API and COM technology whereas OpenOffice use UNO. It means that whole UNO runtime is loaded into memory and is part of the soffice process. The same problem is in startup times - running Openoffice means to run almost whole OS. Of course that users don't have to take care about such argumentation, but I think that we cannot expect any major decrease of memory usage in any near future.
Apparently the built in flight simulator easter egg in OO is slow too.
Aminal - DRUMMS!!
Not to argue about whether or not OOo is more bloated than Office, but George Ou has always seemed to be ranting pro-MS and putting forth statements like this just to get the reaction.
Here's his webpage
And his other ZDNet entries
Also, you might want to check out the comments already posted to his review of OOo beta2
... open office being slow:
... 500$ vs lackluster speed, good compatability, and 90% features of office.
Java, now I'm no language bigot, but Java is slower than C (but more portable without changes in code).
It's a replacement for the most bloated piece of windows software and has most of the same features.
I use OO presently, it's not a speed demon thats for sure. However, A) It's free, B) Keeps me from having to run a windows emulator for word docs and scuh. So it's a win win. The equation would be
Shadus
Honestly, I want to love Openoffice and to advocate it... I have worked in finance on excel, dealing with huge huge spreadsheets and many graphs... Have you tried to plot a 10 000 points graph in OOo Calc vs excel... in excel it is done in less than a second... In OOo the application will freeze for half and hour before slowly starting to display the graph. Cherry on the cake it will conviniently try to write "ROW" under each point in a huge ugly font. After that, changing the data means of course waiting half an hour again because the chart is updating. OOo calc simply doesn't do the job, how hard I wish it would.
\u262D = \u5350
The Mac port of OpenOffice (NeoOfficeJ) is so bloated that by default it starts up in the background when you log in! That's a crappy solution because it sits there hogging swap space until you want it.
I can start Mac Pages, Inkscape, Keynote and even the Gimp before NeoOfficeJ is finished loading. Now that's slow.
Well, according to the Misco catalogue I received this morning MS Office standard costs £300.
At my local computer shop, RAM costs £75/GB, so I could have 4GB of RAM for my machine.
On a price performance comparison MS Office uses 7MB and OO.org uses -3960MB.
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. (Einstein)
Just to attempt to forestall all the Java posts - Openoffice.org is written almost entirely in C++, not Java.
The fix is broken too...
RW
XMl parsing is memory intensive in general. So it does not surprise me that open office would be a little slower in parsing through the xml. Microsoft has been able to keep the APIs for their XML parsing closed to the general public. So if those API's ever see the light of day then Open office would greatly benefit from the code in those APIs.
Again (already pointed it out on the blog) I want to point this out.
2G of cas 2 ddr3200 costs less than office 2003.
MS has been very good at optimizing their software to run fast and have a relatively low memory hit *but* always at the sacrifice of stability and maintainability.
:[
They have also had many years to optimise their code bases. OOo is stil very new and will get better over time. I doubt that MSo will improve.
Now don't get me started on the 1gb plus installation of MSO on my new laptop when I got it from my IT group
JsD
So, why again do we have to use XML for everything? Couldn't you represent a spreadsheet just as well and transparently with something like s-expressions? And then you'd have a tight little parser in half a page of code, instead of a monstrous xml parser that handles entities, namespaces, etc.
What's even worse is using XML for remote procedure calls.
I know there's benefits to putting everything in the same basic syntax, but it's not like it's that hard to translate s-expressions into xml, anyway. With a little extra tool support you can interoperate fine, but keep it simple when simple is all you need. But use XML everywhere, following W3C's "all or nothing" rule, and your app has all kinds of extra complexity whether it uses it or not.
I've tried to use Open Office on my machine at home (dual-P3 800 MHz, 1 Gb RAM) and have always gone back to KOffice. OO has always felt "bloated" to me. It takes much too long to start up, and everything seems to slow down a little on my machine.
On the opposite end of the spectrum, Abiword and Gnumeric load very fast and seem to fly during use. KOffice is a touch slower than Abiword/Gnumeric but still light years ahead of Open Office. It also has a very snappy feel to it. Abiword works on Windows, Mac and Linux. Yes, I know, this doesn't address databases or presentation software.
IMHO, there should be no question mark, but more of an exclamation point.
-Charles
Learning HOW to think is more important than learning WHAT to think.
The responses on ./ and the response from the F/OSS people will demonstrate whether Open Source is superior to Microsoft (or any closed-source company). If people just justify the results and claim that OO is still better just because it's Open Source, then in reality Open Source will lose. I think this is a time for the community to notice the problem, admit the problem, and then try to fix it. If the problem can be solved to the point where load times/memory usage is on par with Microsoft, then the Open Source community will prove that it is competent and able to produce a superior (or even equal) product that has the other advantages (freedom, lack of restrictive licenses, etc) that Open Source brings to the table.
Or... people can just whine and show the world that they're a bunch of babies who accuse people of being shills and just ignore the problem.
I, for one, hope the former occurs. I'll admit I'm not a good enough programmer (yet) to do anything about the problem now, but I hope the Open Source programmers who are capable will tackle this problem and fix it w/o making petty excuses.
Men occasionally stumble over the truth, but most of them pick themselves up and hurry off as if nothing ever happened.
OpenOffice Calc uses up 211 MBs of private unsharable memory
S tring=exact&Acronym=MBS
http://www.acronymfinder.com/af-query.asp?p=dict&
So, Calc is using 211 Mass Broadcasting Systems? No no wait, that's 211 Millions of Bytes per Second.
That's fast!
1. ODS documents are compressed (gzipped?), so large ones take longer to save and longer to open. I love them because I work with phone book listings and ODS files are small enough to email. Here's an example: 1/3 of the Hamilton, Ontario phone white pages is 51.8MB as CSV, 4.7 as XLS (Office 97) and 1.6MB as ODS. I also removed some unneeded data from the XLS version, so each listing is smaller. OpenOffice.org 2.0 opens the larger file sized XLS version five times quicker than it opens the ODS version, but ODS is still my format of choice due to the file size. Now, don't get me started on annoying 65,000 row limits... they really get in your way when you're dealing with phone books!
2. I use KOffice (KSpread) whenever possible because it's much quicker than OOo or Excel. I recommend it to anyone on Linux. Keep OOo around for some advanced stuff, but use KOffice for quick edits and browsing.
The global economy is a great thing until you feel it locally.
Put the other way, extreme processing demands render progress in the hardware field almost moot.
Is ZDNet owned or funded by Microsoft? Seems like every article I read from them is very biased towards anything non-Microsoft. Have you ever seen them do a pro Linux/Mac/Firefox/Open Source artice, ever? I am having a hard time finding one.
I once had to deal with drawing a chart with ~40K data points. I had OOo installed, so I tried that ... bad move.
After strugling with it for 15 minuts, I went looking for an alternative. I found gnumeric, and what OOo could do in minuts, it'd do in seconds!
Gnumeric is full featured, and can save in compatible formats (for both MS Office and OOo). If you do any serious spreadsheet work under Linux, you owe it to your-self to try.
Give bloat an inch, next year it will be back for the mile. Needless IT upgrades cost companies money. It would be better if software folks stopped bloat. Then we could have faster CPUs *and* faster software.
That said, the only time I have found OO to be painfully slow, other than loading, is working with X/Y charts on datasets with more than 2k points or so -- it redraws every point like 5 times every time you mod the chart, and takes a good long time to do it. Too much conceptual abstraction going on there, for sure -- a pitfall of object oriented programming.
Someone had to do it.
if i remember correctly, after compiling oo2, it ran very well and fast. the precompiled bins were def slower. my guess is that these tests were run on a windows machine. so just switch to nix and compile, its that easy.
... an article possibly designed to sink Open Office
Maybe, maybe not, who knows. But what I find odd is that a simple, easily-measureable property like speed is treated as a religious issue and/or examined for conflicts of interest at all. Why not just measure it in a series of comparative tests as scientifically as possible?
And then, if Open Office is found to be lacking in speed, fine, no problem! The result simply becomes very valuable input to OO's design and development team, and in all probability will get dealt with very seriously and rapidly and to the benefit of its users.
There really shouldn't be an issue of contention here, if we're truly techies.
"The question of whether machines can think is no more interesting than [] whether submarines can swim" - Dijkstra
PWN3D!!!
Comment of the year
With the money you'll save using OpenOffice over Office just buy a faster CPU and more RAM. It will speed up OO and still be money better spent.
"A government is a body of people, usually notably ungoverned." - Shepard Book Quoting Malcolm Reynolds
So everything this guy writes is suspect (i.e. wrong) because he ALWAYS takes Microsoft's side on things? Taking that thought a bit further, virtually everybody in this forum takes the anti-Microsoft side, so everything written here is suspect (i.e. wrong). I think that, as is almost always the case, the truth lies somewhere in the middle. Probably Microsoft is somewhat faster because it is C++ throughout, and it is a mature product that has had much optimization work done over a long period of time. It also probably uses less memory because it links with all those DLLs, and it is compiled C++. Conversely, OpenOffice is probably nowhere near as bad as the reviewer states; most likely he found an optimally bad dataset for OpenOffice to make his point.
The more you regulate a company, the worse its products become.
Go to the Options and uncheck the Java option (Use a java runtime environment). After this, OpenOffice.org start like a breeze...
I downloaded OO.o the other day and opened a small ODT file. It didn't have any startup problems, and the interface (if ackward compared to the traditional MSWord) felt responsive.
So clearly it's something SPECIFIC to the Spreadsheet handling. And I recall OO.o being VERY SLOW opening spreadsheets in version 1.4 (or was it 1.1.4? whatever)
Wait.. an article on Slashdot that puts a Microsoft product in a better light than an Open Source product with no snide remarks tacked on by the editor???
Hmmmm....couple this with CmdrTaco suddenly learning to spell...
Penguins grab your pitchforks and torches.. I smell a Microsoft conspiracy here...
There are a remarkable number of OO.o/FOSS appologists here. The answer to this surprising result seems clear to me:
Microsoft makes good software!
Okay, call me a troll, but I've tried a lot of free software over the years and I almost always find it lacking. Microsoft's stuff, on the other hand -- most particularly Office and Windows -- is remarkable when you consider how much they do and how efficiently.
One of the biggest areas in which FOSS is lacking is the boring optimization and debugging that's vital for world class software. The truth is that Microsoft is huge and has lots of money, so they can afford to spend time on that important finishing polish. There's an old saying in computer science: The first 90 percent of the work is easy, the second 90 percent wears you down, and the last 90 percent - the attention to detail - makes a good product.
Who said OSS can't suck? Just because OO's written by a group of geeks doesn't mean it's automagically better than software built by professionals.
As far as I can tell...
1) OOO IS slow - under Windows and Linux, enough so that competing "offices" like KOffice are kept alive despite reduced feature sets.
2) Office runs faster, but for that matter, so does IE - is it any suprise that MS can write software for its own OS which takes every possible advantage of its native environment to run with speed?
3) I use OOO whenever I can, because open standards means I know I'll be able to access my data in 10 years, unlike the struggle I've had with old Office/Wordperfect/XyWrite documents I've had to try to convert.
4) OOO is "bloated" in the same way my big multitool is bloated - you can't be small, fast, and everything to everyone on every OS
Using plain ol' text since 1968
Check out "passive noob"'s comments on OO start up times
This is crazy. I did a little experiment. JRE(Blackdown) on, CPU in powersave mode (800Mhz): 211 Seconds to start JRE(Blackdown) on, CPU in performance mode (1800Mhz): 99 Seconds to start JRE off, 800Mhz: 4 seconds. JRE off, 1800Mhz: 2 seconds.
I know Java fans don't like this, but Java is too slow for competitive apps. This is why it is restricted pretty much to serving as a learning tool and for interfacing with database packages.
I didn't realize how much I hated OpenOffice until I used Word for a while last night. OpenOffice takes about 20 seconds to start on my Linux machine. The latest version of word takes about 3, on a Windows computer with half the RAM and a slower CPU. I've not managed to crash Word in quite a while, while OpenOffice crashes reliably if you paste a figure from, say, Matlab and drag it the wrong way (I have about 20 of those Sun "thank you for your crash report" emails in my inbox right now). And god help you if you want to add captions to your figures, or use "styles", or insert an equation, or do just about anything a good word processor should let you do. As it is right now, I'd rather use Word under VMWare than a native version of OpenOffice. For now, my favorite by far is LaTeX -- even with its arcane syntax, it is a hell of a lot better than anything else out there.
Read this comment for a nice description of why that is not ad hominem.
Your slur on his 2 digit ID, however, is completely off topic. Google for "petard, hoist upon".
Infuriate left and right
I've been saying this for years now and all i got bitching from fanboys. "No difference in my computer" Yeah right, i've installed OOo to 10-20 different configurations and where ever i test it, OOo is horribly slow to start. Slow startup is huge issue for many. Now you say that there is a quicklauch feature, but quess what? Maybe i don't wan't another memory hungry app to backround. (MS Office don't use any quickstart features either) Here's some numbers for you from my laptop. Coldstart: And memory usage (includes VM) OOo Writer: 31.6 seconds (~49 MB) Office Word: 4.8 seconds (~14 MB) "Warmstart": OOo Writer: 17.7 seconds Office Word: 1.8 seconds.
http://archonon.sytes.net/
or is this part of MS's "Get the FAX" campaign?
I know I'm going to get modded down because I'm about to criticize one of the darlings of Slashdot, but I have some karma to burn: The problem with OO.org is that it attempts to be a clone of MS Office rather than a good office suite. I run MS Office using Crossover Office, and it is much faster (I don't have numbers, but it's on the order of 5-10x, even more for some very large documents) than OO.org. I'm not ideology driven - I need to get real work done. For me, that means document compatibility and speed. When I generate my own documents, I use LaTeX and Matlab to produce documents superior in quality to both OO.org and MS Office in an open document format. When reading large documents, OO.org is unstable, is not 100% compatible, and is too slow for day to day use. I tried opening one Word document killed OO.org after an hour, where MS Office opened it in a minute or so. Bottom line - why _should_ I be using OO.org? It suffers in compatibility on the reading side, and doesn't generate true publication quality documents on the output side. I understand that document compatibility issues are really Microsoft's fault, but, again, I have to be pragmatic. A couple of hundred dollars is negligible compared to the value of my time.
both start up quickly and provide excellent functionality
Dear Mr. George Ou:
We'd really appreciate if you provided us with the spreadsheets and documents in question, so we can run a benchmark and/or analyse possible memory hogs in OpenOffice.org.
Thank you very much.
Sincerely,
Your friendly neighbor Spy der Mann.
I have OO 2.0, and Office 2003 on a Dell with 1gb RAM and a 2.66Ghz P4. I have the quickstarter loaded for OO, but not for MSOffice. Calc takes twice as long to load as Excel, Writer takes easily 3-5 times as long as Word on identical files. This is true when including starting the app itself, when the app is already open, the times are closer, but OO is still slower.
I have a spreadsheet that takes 15 minutes to open. About 20 rows and 3500 columns with a lot of simple formulas that took only seconds to recalculate in its entirety when the spreadsheet is already open, but for some reason takes 1000x longer to load when I close and reopen the spreadsheet, saying "calculating" in the status bar. I'm guessing there's at least one bug relating to this.
This is my only spreadsheet that gives me this trouble. I have many many larger, more complex spreadsheets that I work with in OpenOffice 2 without noticeable slowness.
Anyone who has run OO on Linux knows very well that it is bloated. Not only is it bloated, but it uses some homegrown toolkit for the GUI. I won't even use OO, personally. Normally I don't have a use for an office suite, but when I do I'd rather us MS Office, which isn't a problem because I now have a Mac sitting next to my Linux box. Of course, I have never paid for MS Office. Maybe if I had to pay for it I wouldn't use it.
I'm sorry, but OO is one of the worst examples of what open source is capable of.
-matthew
"THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
http://www.lanarchitect.net/Examples/200264-l.zip
s /200264-l.zip
(And the obligatory coral link)
http://www.lanarchitect.net.nyud.net:8090/Example
OK guys, time to benchmark!
Honesty is more important that cheapness. (Exceptions ... ???)
Saying it's because XML parsing is slow doesn't make sense. Any decent XML parser
will parse at a 30 MBytes/s rate on a recent processor, usually one waits for I/O
it rather how that XML data are handled that makes for a slow loading, not the
XML format itself. 2 minutes of processing would mean like a multi gigabyte XML
file, that's not the problem.
Daniel
java is the problem, turn it off and openoffice loads tons faster
The author of the article had documents to back his claims. They may be specially tailored to make openoffice look bad - but I doubt it. In my experience, OO Calc is a pig compared to for example gnumeric - and that, quite frankly, sucks.
:)
I only use OO to view documents various people send me. That's the *only* thing I use it for. When I write documents, they're either written in HTML (using quanta), or written in lyx (to make them pretty and printable!
Some of the software available as Open Source unfortunately sucks quite a lot. In my opinion, OpenOffice is one of those pieces of software. It's nice for compatability - but it sucks in usability.
"Rune Kristian Viken" - http://www.nwo.no - arca
I think EMACS is closer to 50mb these days.
Every single article this guy puts out is heavily slanted, neglects to take into consideration loaded objects that Windows preloads and extremely anti-open source. I have yet to see him put out one article claiming anything that is open source is good.
If Microsoft isn't paying him, he must own stock.
This is my sig. There are many like it but this one is mine.
This article is missing the point of OpenOffice. It doesn't take scientific results to find out OpenOffice is slower to open files than MS Office. Anyone using them will see the difference in a big way regardless what data they use. The fact that it's slow to open files and uses more memory is the primary issue with OpenOffice. The fact that MS Office can't retain compatibility accross versions is the main issue with MS Office. The point here is that OpenOffice is the first software in years that is on par with MS Office. They are both 'comparable'. People may argue on which one is actually better, but for the first time they are both pretty damn close in what they can or cannot do. Why is it important? Because on every single other aspect OpenOffice wins hands down. It's free, while MS Office costs hundreds. It's open source and totally customizable, while MS Office is closed. It's free of patent issues, while the state of Massachusetts found MS Office's proprietary format isn't. That's what counts. We finally have a real alternative, that is for ever free, and documents created by it will always be able to be read by any application implementing this open standard. So sure, shout out all day long that OpenOffice uses too much memory for your taste, but at the end of the day, it still wins.
OOo is VERY bloated.
At least when you compare it to MS Office 97. MS O97 was FAST.
Compare it to MS Office 2k or 2k3, and OOo is MUCH faster, at least in my experience.
Shiny. Let's be bad guys.
Hmm, I wonder if it's the dollar sign in the file name? Perhaps renaming the file will correct your problem.
"Sufferin' succotash."
His table compares the time it takes OOCalc to load an ODS and SXC document with the time it takes Excel to load an XLS (or XLS-XML) document. Now that's not the same thing.
He should compare the time it takes OOCalc to load an XLS document with the time it takes Excel to load it. Sure, maybe Excel wins here by a few seconds.
Now compare load time of the ODS document in OOCalc, which takes three minutes (it says there) with the time it takes to load it into Excel. I predict that will be at least three years, if ever...
OO Wins!
Baz
The tests were done in Microsoft Windows, so the test is biased.
No Linux based test was done for Microsoft Office, so, since Windows is MS Office's optimized environment it will obviously do better there.
The same logic applies to OpenOffice. No optimization in the environment, worst results.
A Linux test would show OpenOffice running better than MS Office, since that is it's optimized environment.
The test is not sound, and it couldn't be. Not at this time, since no unoptimized version of either works in a neutral Operating system.
When MS does something right and better, it is because MS cutting corner and cheating. When OSS does something bad, it always has some justifiable excuse. This kind of attitude is not going to be good for OSS.
That's a good point - money spent on better hardware is better than on a single piece of software - unless you don't have an alternative, of course.
Pain is merely failure leaving the body
XML is a data interchange format. We've finally arrived at the era where apps can interchange data in XML without (necessarily) being trapped in a proprietary data format. But that doesn't make XML suitable for internal data representation. Apps should use internal data formats that support their native performance, and serialize data objects to XML for interchange, including storage. Using XML internally when performance thereby suffers is the bad kind of lazy, bad design that saves development time at the manifold expense of user time.
--
make install -not war
I don't want to be an apologist for OO but you can't deny the fact that MS has had about 10 years long to get MSO right than the OOo people have had to get OO right. Now that isn't to say that we should or will have to wait ten years till OO is as good as MSO is today but we should cut them a bit of slack if the software isn't a slick an lean as it could be. In a very short period of time the OOo team have gone from nothing to something that can rival MSO. Assuming the pace of development continues OO will, I feel, be as good as MSO in two years.
I used to have a better sig but it broke.
Microsoft Office: $10 per 1 second less load-time
Here's a link that contains recordings from an openoffice conference. One of them talks about the slowness of openoffice.
http://ooocon-ljudmila.kiberpipa.org/media/
OO is only better than MS because you don't have to pay for a bloated mess. The best office package I've used is Lotus Smart Suite. I'd be glad to pay a three digit sum for a cross-plattform version (Linux/OS X/Win) of that office package.
We suffer more in our imagination than in reality. - Seneca
I realise you're trying to make a statement with all your telnet to port 80 instead of using a browser and such, but I think you should at least have used a compiler to build OpenOffice.
proof, n. A demonstration that a conclusion is implied by certain premises and axioms.
So this is an interesting thread, and I thought I'd take a look at my own situation. There's something odd going on here, and I'm not sure what it is in OpenOffice that does this.
I started OO on my Debian Linux (Sarge) Thinkpad T40 (my original article on this) while doing my normal workload (Evolution, IRC, etc etc). As soon as the main Frame appeared, I clicked the [X] close button to exit it - assuming that OO's main startup thread would have completed, and shutdown processes are pretty fast. My first timing:
dbs@hunter:~$ time openoffice
real 0m30.440s
user 0m3.084s
sys 0m0.216s
This is not a particularly fast laptop (1.4gig), but not bottom of thel ine either. That's not too bad to start up a whole office suite.
But, I decided to try a few other things, so from the same command line, I did it again. It came up VERY fast:
dbs@hunter:~$ time openoffice
real 0m3.475s
user 0m3.104s
sys 0m0.128s
Nothing in 'top' is showing memory cached or in use or anything. I know that Microsoft uses a 'quickloader' to keep things like Excel and Word in memory between uses, so there's a memory hit in favor of faster startup, but I wonder if OO does some sort of environment checkup on start each time, and remembers setting between restarts (in a gconf config entry maybe?)
Now, 10 minutes later, startup is still only 3 1/2 seconds or so.
There's so much mystery and hand-waving in Microsoft products, that benchmarks like what this guy is talking about are nigh on useless, and saying that OO is 'bloated' is playing to the knee-jerk folks who constnatly rail "BLOAT IS BAD!". Bloat means useless functions inside a product that have no end-user need, and are added to the size of an application in order to appeal to a very very narrow audience (or just due to bad design). I don't think OO is in this category at all.
As far as the filesize loading problems, I have yet to try this out, but I shall, and will report on what I find.
Event Management Solutions : http://www.stonekeep.com/
I use notepad.
OO is pretty usuable, as long as you have a very large amount of RAM. I upgraded my thinkpad from 256M to 1G and openoffice load times went way down ( probably ~5x under some circumstances).
I'm not at all familiar with the architecture of OO or what the developers priorities are, but it'd be nice if a bit more time was spent on performance. Firefox could also use work here also.
I'm sure that OO wants to concentrate on features and compatability. That's certainly a worthwhile goal, but perfect compatibility seems pretty much hopeless, and you can always think of more features to add.
The Microsoft's XML size is 188 MB(197,521,133 bytes). The OpenOffice's SXW size is 3.59(3,770,916 bytes). Would you prefer to email a 188 MB file or a 4 MB?
I miss you, where are you?
I like OOo and recommend it to any of my friends who will listen. I got v2 and still like it a lot, even though it is still slower than Office (opening, saving, etc). Jeez, wonder if it has anything to do with java? Of course, I have been flamed previously for suggesting that java is slow, so I will say that java is the best ever. It's neato and way rad. And super and stuff like that. Right.
Anyhow, one interesting thing I noticed is that when I converted some docs to the OpenDocument formats, the file sizes are nearly twice as large. Not that document size really matters anymore (my cheap PC has an 80G HD, and yes, I left the door open for someone to reply to this and get some funny mod points with that last stmt and closed it with this stmt). It does make me wonder, though, if part of OOo's sloth is that it is rendering / creating XML documents rather than the old file format? If that's the case, I am sure in time it'll get better. Plus, if M$ were to ever adopt OpenDocument (riiiight) I'll bet they'd have the same problems.
blah blah blah
This is one area where Open Source has its weakness.
Cutting down and optimizing existing code is not nearly as glorious as adding new features.
Micro$oft, on the other hand, can afford to have a whole team of programmers who's only job is to optimize and slim down the code.
As much as I hate MS, they did get a lot of things right in Office (except for that damn paperclip).
Remember folks, slashdot doesn't have a -1 "disagree" moderation!
MS Office is more efficient at handling its own closed format files than Open Office 2.0. Who would of thunk it?? Look at the time differences. Apart from the specially crafted spread sheet, we are talking about tenths of seconds for MS office as opposed to one or two seconds for OO. Generously assuming the average worker opens maybe 100 documents a day, we're talking less than two minutes a day difference. People waste more time than that scratching their buts. I'm not saying this is not an issue which should be addressed by the developers of OO, but to sensationally report that OO is seven times slower without giving equal emphasis to the number range you are really talking about(tenth of second vs. 1 second)smacks of the usual marketing FUD from Redmond. Also, there is no indication that any care was exercised to insure that the documents used in the test are representative of the types of docs encoutered by most people. I strongly suspect they were chosen to cast OO in the worst light possible. I have opened many .doc documents with OO 2.0 and did not notice any significant time lag(less than half a second for typical 100KB .doc file) although its obviously a little slower than MS Office.
So what you have here is some self appointed blogger with an apparrent axe to grind against open source posting his supposed test of OO and MS Office in a skewed and sensationalist manner and with results that are contrary to any real world experience or concerns. This is not news; it's marketing FUD.
OO writer starts in less than 10 sec's on my K7 1.4GHz with 1G, and that's with no quickstart. (Disabling java only cuts that marginally.) I can live with that.
Remember, that the entire windows OS is the "quickstarter" for MS Office. All the dlls and IE stuff are already loaded.
...Comprehensive ...Freedom ...Working
Pick any two.
Nobody has mentioned gcalc yet? It's about a billion times faster that OO Calc and has many times more useful features.
Because they don't care about "legal". Often when I tell someone about OpenOffice, they tell me it's neat but they already have MS Office at home - or at least word. If you tell them "but it's free", they often say they got the MS products free too - illegal of course. They figure why get some free knockoff when they can get "the real thing" free. The ones who paid for MS often got a student price or something, and they really have no incentive to switch until their existing version won't work any more.
The problem is that everyone has Word or Office already weather they paid for it or not. In that context, OOo has nothing to offer - the other benefits are too abstract for joe sixpack. It's a case where MS benefits from casual copies floating around.
The situation is the same for others: Mechanical Engineers tend to have a pinched copy of Autocad at home. Artists have a pinched Photoshop. Animators have a pinched copy of Maya. This hurts adoption of GIMP and Blender - sorry, there is no great GPLed CAD program (except for QCAD for 2D). I'm sure there are plenty more examples. If Longhorn can prevent people running illegal copies of all this software, we'll start to see people switch - assuming MS will allow them to run the legally free stuff.
I was a little concerned that Calc might use up 211MB of memory, but it didn't sound right so I checked it myself.
The OpenOffice binaries on Windows use up just over 40MB when OO is "closed" (e.g. the quickstart program is still in memory).
When I launch calc, that number shoots up to an astronomical 42MB. Heh. Opening a few fairly simple spreadsheets in MS Excel format and the number goes up to 60MB.
Excel (2002) on its own uses 15MB when it's running empty, and opening the same few fairly simple spreadsheets jumps that number up to 21MB.
So yeah, Excel is smaller in memory. I also find it to be much more responsive. But Calc is not 600% bigger for crying out loud.
Anyhow, sorry for the lack of details but I don't feel like going into detail. I'm on XP SP2 with 1GB RAM. Office XP 2002 and OpenOffice 2.
Eighty Megabytes and Constantly Swapping.
Emacs grows to fit the available space. Or at least it did when it was still growing.
It seems all the competent hackers have lost interest, because everybody has been
trained not to understand lisp.
-I like my women like I like my tea: green-
Circumstantial ad hominem (poisoning the well) is using the particular circumstances of the messenger to attack his message. It is indeed a fallacy, even when the claim about his circumstances is factual. Specifically, it is a fallacy of relevance, because those circumstances are irrelevant to the truth or falsity of a conclusion, or the validity of an argument.
That isn't to say, though, that recognition of bias, or the increased potential for bias arising from circumstances, is not useful. It does play a role in "critical thinking", because it serves as a flag for taking a more critical look at the statements to spot flaws in the facts or the reasoning. But relying on those circumstances to discount what he has to say is itself a flaw in reasoning.
Ipse dixit is a different issue: appeal to authority.
Believe me, I'm 100% for Open Source, but lets cut the bullshit, if an application is even only 5 times slower to do essentially the same task (which means exactly what it means) then I said you can't start blaming it on how the files from one are better compressed or the internal is in german or other things, it is just 5 times slower whatever you said. I'm not saying these are not valid explanation, I'm saying it is counter productive. Yes it's free, but that's not an excuse, Open Source is also about doing better software, not only cheaper ones!
I don't like Microsoft. I don't like Windows. I do, however, like Office. It's been a good office suite for a very long time. It's been very easy to use since I first started playing with Office 4.2. If Microsoft would actually release a version of MS-Office for Linux then I would probably purchase it.
Before everyone starts ranting about how this isn't good for GPL, or how I'm being bad by saying this, remember, the point of the GNU OS is for application developers to have a level playing field. Microsoft, like any other consumer software maker would be just as correct to participte in that kind of market as anyone else.
I use Open Office, but I don't agree that it's the best productivity suite. It is the best free productivity suite for Linux at the moment. Since Microsoft's product will always cost money, Open Office undoubtedly will remain the best free productivity suite; it will serve as a baseline. If vendors wish to make a commercial product that is better than Open Office and charge for that product it's their right to do so.
Do not look into laser with remaining eye.
Just one question: What do you expect for paying NOTHING? Oh no! It takes a couple more minutes to load! Yup, that little feature is worth running out and paying $300.00 on MS Office. Put it all in perspective, people. Open Office is FREEWARE. And, as such, I find it an excellent value.
heck.. who even needs OpenOffice, when you have ex!
Have any of the people whining about code bloat/performance actually bothered to run a code pofiler on OO?
If you don't like it, use the source and present a solution.
If someone is passing you on the right, you are an asshole for driving in the wrong lane.
I used the data you suggested. My methodology and note-taking aren't perfect, but here's the lowdown
On a 3.06 GHz Intel with hyperthreading on (though it makes no difference) and 2 Gig of ram
OO 1.9.122 vs Excel 2002 SP3
3.4 Meg SVX file vs 191 meg xlm
File load: SXC OO ~3 minutes , XML Excel ~ 1 minute (not including time to unzip and open from withing excel).
Memory use (meg): min/typical/max OO 13/115/212 excel 4/45/65 (yes, 4 meg with a 191 meg file open, go figure !?!?!)
proc load: 100% during load times for both on "1" processor (HT did not help)
I saved the sxc file as ods and xls versions (hadn't figured out loading the zip into excel at that point). 3.9 meg and 49.5 meg file size repectively.
File load: ods OO ~1 minute, xls Excel ~3 seconds
Memory use (meg): min/typical/max OO ?/72/72 Excel ?/91/91
proc load: 100% during load times for both on "1" processor (HT did not help)
Seems the Excel has some advantage in extreme situations but the caveat mileage may vary seems to apply.
If OO would run twice as fast or use half the memory, I'd be willing to pay twice as much!
The world is made by those who show up for the job.
I think it is clear that for large sheets (at least for this example), OpenOffice 2.0 calc is unusable. I am gusssing that there is a quardratic data-structure/code somewhere (without knowing anything about the source code, I am willing to bet that each time a row is needed, all the rows are scanned; or something like that).
On the other hand, this is a
This may be an unusual concept, but what if MS's Huge Team of Developers have actually put out a refined copy of office, and OO being open source, hasnt reached that level yet?
His two complaints are one and the same: that OpenOffice uses more RAM than Excel. I have 2 Gb of ram in my machine, and his 16-sheet file loaded in one minute flat, not three as his benchmark showed. This is within 25% of the 47-second time that zipped MS XML loaded in Excel, which should be the most useful comparison since OpenOffice uses zipped XML as well. So, it doesn't seem there is a huge processing difference between the two engines; the difference is much more likely that he was swapping memory out to disk. My conclusion: Fix the RAM problem in Open Office and this issue evaporates.
The Mac version of Office is IMHO quite superior to the Windows version. It just works and it is much more unobtrusive. My main gripes with the Windows version have been it offering a little too much help when I just want to get some work done and the sometimes seemingly random manner that it shows special toolbars. Never had any of these problems in the Mac version. I hope someday they port it to Windows, even! ;)
This article is so biased and misleading it's not funny anymore. That's George Ou for you, bashing open source software again. It is sickening.
I kinda have to ask since this makes no sense to me.
How the hell is 1 second load time making the news? I mean really.. it's 1 second, over a week if you open OO every work day thats all of 5 seconds. So what a minute a year is going to some how make the world come crashing in on it's self?
I like muppets.
That's truly awful design for this kind of application. I suppose you're going to tell us next that's it's also statically linked!
I can handle a few microseconds of delay or extra memory usage in return for a free software product that's a great alternative to MS Office.
Besides, Microsoft is evil.
The bottom line is that just about *all* software that comes out these days is
bloated. Perhaps someone who is an expert (or at least codes for a living instead
of personal use) can comment better - is it just bad assumptions? Bad technique? Bloated libraries?
As an example, and not to pick on java, I use a standalone java application
daily. The first version was released about four years ago had a working set
about 8Mb and a virtual size of about 50Mb. The latest version comes in at about 60
and 250. Yes there have been enhancements, but the primary function remains the
display of real time data and is little changed.
Further, my daily running desktop applications, which have been more or less the
same for 7 years, now requires a commit charge under XP of 850MB and often near 1.2Gb (glad I have 2GB. Five years ago the same (under win2k) would have been 300-400Mb. I can't point to any great increase in features or usability to warrant this increase use of resources.
I'm soooo glad that OOo 2.0 only uses 211 MB of RAM as opposed to 221 megs for 1.1.14. Now I can get rid of that swap partition...
Now... As Computers get faster, and an Office Suite begins to provide more features than the average user even would think about using, what is the drawback to OpenOffice? yes, I know ooCalc2 sucks when it comes to scientific graphs and stuff. But does the average user ever do that? No!
I personally believe that for the general population, Processor speed and updated software is reaching a plateau. I mean, what else do you want in a word processor? Combine this with a massive amount of spare CPU cycles, and people are going to see that shelling out a couple hundred bucks for features that they won't use is ridiculous, and a reason against it definately will not be that they are concerned with their RAM having a quarter dedicated to their office suite. It does what it needs to do, and it does that for free. That's all that will matter.
I may be wrong but you're downright ugly!
Far less employee time is wasted waiting for Open Office to run than is wasted on Freecell
[root@lx OOo_2.0.0rc3_src]# find . -name '*.c' -type f | wc
271 271 7711
[root@x OOo_2.0.0rc3_src]# find . -name '*.cxx' -type f | wc
10802 10802 471294
[root@x OOo_2.0.0rc3_src]# find . -name '*.java' -type f | wc
3250 3250 196385
The Java appears to be what slows things down but if you point that out you seem to get modded down around here.
I don't think Java fans can handle the truth.
I converted sxc to xls (see other post). Excel opened it in ~ 3 seconds. OO 1.9.122 opened in ~ 20 seconds, but used 137 meg. Would have opened in half the time except for all the auto row height stuff that it did. I'm beginning to suspect Excel is optimized in 2 ways: code size & IO speed. I suspect the IO speed trick is to only load what it required since the HD is busy whenever I go to another part of the document.
The world is made by those who show up for the job.
I'm not sure how feasible it is to profile such a large program, but I'm sure Microsoft profiles the daylights out of their stuff. Do OOo developers profile things like the start-up time? After all, you can't start optimizing things unless you figure out exactly what is slowing it down. Is it the Java run-time engine? Is it because it needs to load a lot of libraries that MS Office does not need to (because of dynamic linking to Microsoft DLLs). Maybe when loading certain data sets, the program goes into a pathalogical state, creating hundreds of thousands of small objects? I don't know.
But things like analyzing profiling data and then optimizing are not fun to most people. Even more so if it means that an algorithm needs to be re-written. After all, if the "open file" operation needs a complete re-think + re-write, who's going to do it? It's not "fun". After all, the "open file" operation already exists. Generally, I think programmers like to build *new* things as opposed to fixing old things. And in this case, it's not even a matter of "fixing". It's a matter of rewriting. I presume that at Microsoft, if Word's "open file" operation (run with me on this for a minute) is uber-slow, then somebody is going to *have* to fix it, or not get a good performance review/etc. However, in the case of OOo if no one makes it faster, well, it does not negatively affect the person who wrote the slow version in the first place (not to discredit OOo authors or anything. They've done a phenomenal job given that they do this for fun and not profit).
Of course, there are an equal number of programmers who like to fix security holes and so forth, but patching a security hole is one thing, while re-writing major algorithms in a large program is another. There are of course some programmers who love optimizing code (Michael Abrash?). But I think they are far and few between. Very often, once something works, an attitude sets in that "It's working. Now don't break it". And optimization in it's early stages will often break things.
If Office uses zero MFC, then it should be safe to delete that file, right?
One line blog. I hear that they're called Twitters now.
What ?! Open Office bloated ?!
This belongs in the "is this news?" category.
Many people wrongfully take it for granted that Open Source software is always better on the back end.
I was wondering how much of the RAM footprint difference was due to Office relying on Windows code. So just for the fun of it I fired up Excel on my Mac. 22.94 MB of real memory being used for Excel, 34.14 for Word. Compare that with 7.10 and 9.81 for Excel and Word on Windows and 37.54 and 37.66 for Calc and Write on Windows. Anyone running OpenOffice on a Mac want to add another data point where MS doesn't have code "hidden" in the OS?
OpenOffice is really a partially-commercial product, which may explain why it is the way it is. However for most OSS I feel the opposite of what you say is true. Programmers do *not* work on features, instead they work really hard on making the part that exists as fast and elegant as possible.
Now before you say this is good, remember that the unimplemented features includes things like documentation, installation and configuration programs.
My suspicion: Calc is holding a parsed XML document tree for the spreadsheet in memory, while Excel reduces it to an internal structure and recreates the XML when saving. Holding the document tree makes for more memory usage, but it allows for preserving of unknown XML without mangling it. Parsing to an internal structure is more efficient, but anything not recognized will be lost when saving.
NB: I don't think Calc works on the parsed XML, it probably has an internal representation to actually work on which is then tied back into the XML document so the XML can be updated to reflect the changes in the data.
"Wife! I NEED a new dual-processor multi-gigabyte machine. No, OF COURSE, it isn't just for games. How could you think even think that."
Nonetheless, I'm finding that I'm opening Abiword about 1/2 the time these days. I was a WordPerfect fanatic in the day but since Word set the standard for lowest common denominator for slapping simple text on the screen, I'm finding that Abiword fills those needs nicely a great deal of the time.
It is alright if OpenOffice.org uses more memory or is slower. The strength of the product is the process of community involvement and the ability to change. This might focus the community on memory useage, which would be a good outcome from this article. OOo has other strengths, such as cross-platform, price, PDF export, no need to track licenses (very expensive process), etc.
I'm using Office 97 and OOo 2.0 on Win 2K. I'm using the OOo Quick starter, which means that soffice.bin is resident and taking about 15M. I'm also using MS Office Startup, which is soffice.exe taking about 1.1M. When I start Winword.exe it takes an additional 7.5M, and open a simple document that merely has the text "This is a test" it take another Meg or two, and only takes a second or two. Now when I open an OOo document (.odt), there is no other process that starts, but soffice.bin shoots up to 42M! However, it opens in two seconds.
So, while I do see more memory usage, a real speed test is not really very different. I suspect in the article, he is not using the OOo quick start, whereas he is using the Office Startup. And how much Office stuff is being hidden by it's hooks deep into the OS, and thus it's startup time is part of the OS startup.
This is not to say that OOo couldn't be improved. I'm sure it will be. But OOo 2.0 is an excellent tool to have in anyone's toolbox.
Peace,
Jim
"You clearly don't know what an ad hominem attack is."
The GP does indeed appear to understand the subject. I think the confusion lies in the fact that there are various types of ad hominem attacks. In this case, this is what's known as a circumstantial ad hominem.
The wikipedia article explains this well. If you believe the wikipedia article to be incorrect, you may want to take the time to edit it.
"But when Ou, who has a long and easily verifiable history of writing articles that disparage open-source software, says the same thing, his words should be taken with a generous pinch of salt."
Ironically, you have made an ad hominem attack yourself. From the wikipedia article:
But I'm not surprised that you're incorrect, since Anonymous Cowards usually are. ;-)
Sitting in my day care, the art is decopainted.
There should be much more to this test.
It should be dismissed as crap.
I am happy the OpenSource community is talking about what a horrid mess OpenOffice is. I like and use OpenOffice. But I have noticed that OpenOffice takes a LONG time to launch the application. And I have noticed that it takes a very long time to open documents. And OpenOffice tends to crash on occassion. On the other hand, it is free to use. So, like the article says, I have to choose between time and price. Shelling out $300 per computer is just not an option for me...so, there ya go.
I think the solution to the problem is the forking of the OpenOffice project. Personally, I use only the word processing and the spreadsheet programs. I think that most people only use these two parts of the program...so why not focus on these two? Make them the best. Make each program functional apart from the other. Make each of them lean and mean.
The problem with OpenOffice is that Sun is providing the code. Thus, the openness of OpenOffice is tied to Star Office.
As an end-user, I hope the developers of OpenOffice make it the industry leader, not the industry's Yugo.
This surely is the proof they need that OpenOffice is GOOD FOR HARDWARE business, as it compell users to upgrade to more memory, faster CPU(s,) bigger hard drives...
Microsoft office costs infinitly more to purchase than OpenOffice.org.
http://www.popularculturegaming.com -- my blog about the culture of videogame players
After playing with the test files (only on OpenOffice mind you, since I don't run Microsoft software), I have to say that I'm a bit surprised by the performance. The XML file used by Excel is 147Mb in size, and yet winds up taking only 47MB of memory when loaded. I'm a little puzzled at how it can rip through 147MB (of XML no less) in only a few seconds though. With the huge memory requirements for OpenOffice, I can't help but wonder if it's storing the entire XML DOM in memory.
Whatever the case, the development team should really focus on this. Waiting 3 minutes to for a document to load (as well as saving to an alternate format) is excruciating. In fact, OO crashed while saving that test file to the ods format.
I say that Microsoft is about $500 too bloated. That extra 5 seconds on initial load, and 2 seconds to open a file are worth the half a grand it'd cost for me to purchase Microsoft Office 2003. Ehh, $499 for an office suite, I tell you, that's just insane. I'll stick with OpenOffice.org thank you ver much, it's more than capable. Happy business user of OpenOffice.org since 2002.
Technological advances render all but the most dramatic processing demands almost moot.
It used to be true that a given process would be run exponentially faster over time by the growing power of processors. So if you wrote bloated crappy code, within two years it worked fine because all the processors got better. The problem is that we're running into a wall as to how high they can clock the processors because of the heat and power requirements.
The solution has been to switch to a multi-core processor that runs at the same or even sometimes lower frequencies. This works great but it has one HUGE caveat: the code must be able to run in parallel. Code that is being written today, by and large, doesn't account for this. Sure there's threading and all that in much of today's code, but not quite such that you're seeing those same exponential increases in performance.
To write fast code today you have to be able to write code that can break down into numerous discrete chunks that can all work in parallel. With each new generation of processor, this is going to become more and more critical. Right now we have 2 cores, then we'll get 4, 8, etc. With each generation, you'll get faster performance, but with each generation, the code becomes more complex because it must be broken down into smaller pieces to take advantage of the extra cores.
Having said that, I suspect that the OO people are, at the moment, more focussed with creating functional parity between OO and Office. Sure, sometimes it will be noticebly slower, but if it can do everything Office can do, then they can refactor the innards down the line to improve performance.
This sig has been temporarily disconnected or is no longer in service
Look at your "desktop".
What Java Apps are running?
What C/C++/C#/ObjectiveC apps are running?
(Whaps moron over the head).
Do you "get it" now?
I agree with the parent post. XML's strengths are its near human readability. Which makes it easy to design or debug software that uses it to exchange data. But it is a wastefull format for storing information. XML is data bloat.
Think Deeply.
This kind of analysis comes up from time to time. It will come up again. I'll take OpenOffice.org over the proprietary alternatives because OpenOffice.org is free software.
I'd rather have a slow free software office suite than a faster proprietary office suite. If I cared enough to fix this in OpenOffice.org, I could do it or hire someone to do it for me. But I'll never fully learn what the proprietary alternatives do when they run, I'll never be able to fix the things I don't like about the proprietary software, and I'll never be able to help my community by sharing improved versions of the proprietary software. I want fast programs but not at the expense of my software freedom.
When this issue is framed in the terms the open source movement uses, proprietors can often gain (or keep) a client. This movement doesn't object to proprietary software, it claims that when more programmers have access to the program's source code and are allowed to change it, the program may see some improvement. This philosophy is one which places business priorities first. The social and ethical effect on the public—the helplessness one feels with programs they can't inspect, change, or share—is reduced to "ideologial tub-thumping" by the Open Source Initiative, which started the open source movement and defines the term "open source". Free software, on the other hand, places a philosophical focus on caring about society, not chiefly business interests. The free software movement talks about giving me the freedom to decide how the program should work for me. This stresses placing the limitations of what I can do on me: I get to choose how much programming I want to learn and I get to decide someone else to do for me. And, most importantly, the free software movement celebrates the spirit of voluntary cooperation, what keeps society from being a dog-eat-dog jungle. I don't object to the open source movement's priorities in themselves, but I don't think they go far enough to help improve society, and I do think it is computer user's job to care about what kind of society we are allowed to have.
Digital Citizen
Surely EMACS stands for Eventually Malloc's All Computer Store? :-)
If a file can't be created with cat(1) then it's not worth creating.
Agrajag: "Oh no, not again!"
We have a mixed environment, with mostly W2k servers and about 800 clients, half of them Macs (10.4). Users have a user-directory on a file-server, with a roaming profile.
First time a user logs in, and starts Word, Word plants over 80 megs of fonts into the users' profile.
All 2000 users... In groups of 20 or more.
That's 1.6 gig within 10 seconds... ever heard a server choke?
And we surely enjoy storing 160 gig of MS-fonts on our raids too.
All those moments will be lost in time, like tears in rain. Time to die.
I'll begin by saying that I mostly use Linux, and I use OpenOffice even on Windows when I can help it. One reason is that I don't want to give money to Microsoft, but there are other reasons as well, including my belief that Free Software is the key to the advancement of IT in the future.
But this situation is pure hillarity. OSS fans have their list of reasons why Linux (or some Linux app) is better than Windows (or some Windows app). Two reasons near the top are that Windows is slower and more bloated. These reasons are sited often and are part of the OSS mantra.
So I find it incredibly ironic that now that the shoe is on the other foot, the tables are turned, etc., that these very same people are dismissing "bloated" and "slow" as unimportant.
No, you idiots. "Bloated" and "slow" are ALWAYS bad, even when they apply to an OSS application. That means there's something wrong with OpenOffice.org, and if you have half a brain in your head, you have to accept that it's broken for that reason. That doesn't mean you should stop using it or feel disillusioned. And defending your beliefs in the face of this embarrassment just makes you look stupid and inconsistent. HAVE SOME FREAKING STANDARDS, and have them ALL THE TIME, not just when they make your favorite thing look better. It's time for you to have egg on your face, admit it, and take it like an adult. And then the next thing you need to do is stop wasting your time and fix the problem.
I was wondering how much of the RAM footprint difference was due to Office relying on Windows code.
Good question.
I use Open Office on Linux everyday at work and don't see it being as slow. Can we see some benchmarks of Open Office running on Linux/MacOS/FreeBSD/Solaris?
-Joe
Emacs compiled for windows (20.7.1 i386-*-nt5.0.2195) uses 5,420K (says the control panel)
Not much bigger once it loads a trival C++ file and therefore loads cc-mode.
What you are saying is reversal of proven tendencies.
In short, I say... Rubbish!
There are excellent open-source programs as well as bad ones. But I don't know very many that are full of bloat caused by unnecessary, unoptimized code.
Microsoft is no idyllic ship of disciplined software engineering. When was the last time you found a **flight simulator** inside Gnumeric? When was the last time you discovered a half-brained implementation of a dialog or complete feature in Monoposoft Word? (Clippy isn't the only instance of useless crap.)
I don't find OO to be intolerably slow. However, for those who do, someone else has pointed out that disabling Java improves the performance of OO significantly.
Whatever the foregoing arguments, the TREMENDOUS advantage of OO and most FOSS is something that Microsoft cannot TOUCH: Cross-Platform Functionality.
I edit OO documents at work, take 'em home, edit in OS X and FreeBSD, and take 'em to work the next day. This kind of flexibility and convenience outweighs the few virtues that Redmond can claim for MS Office.
Rich And Stupid is not so bad as Working For Rich And Stupid.
FIX IT!!!!!!
\m/
Well said. Defending bloat and sloth in this case sounds almost as hypocritical as Microsoft arguing for open standards in every instance where the proprietary standard isn't theirs while arguing that their proprietary standards are in the best interest of the consumer.
god help you if you want to add captions to your figures, or use "styles", or insert an equation, or do just about anything a good word processor should let you do
You know you're old when you parse a statement like this and the first thing that comes to mind is "figures? a good word processor should process words".
It still amazes me that we're using word processors to do desktop publishing. And get off my lawn!
Endless arguments over trivial contradictions in books written by ignorant savages to explain thunder in the dark.
I just took a look at the Prefecth folder on my WinXP box. It looks like there are links there for Acrobat and Firefox stuff along with a whole lot of other stuff.
Does this mean that prefetch happens automatically for frequently run apps? If so, why wouldn't OOo benefit from this as well? Is it not structured in a way that Prefetch can help it?
Posted from my Android phone. Oh, I can change this? There, that's better...
> nothing makes me aware of how much I need to upgrade my processor like starting OpenOffice.
That was the old deal between Microsoft and Intel. Microsoft would release software that would be ever more bloated and slow to drive sales of new hardware. But they haven't been keeping their end of the deal at Microsoft these last few years. XP was more bloated than 98/ME but not by enough to justify a 3+ GHz Processor. Of course ANYONE who makes a deal with Microsoft eventually gets shafted, it is just in their nature.
But still, Intel can't afford to overly annoy Microsoft even after they got shafted by them yet again by Microsoft picking IBM/Power for the Xbox 360 over Intel.
But I am suprised they aren't quietly pushing OO.o on exactly the ground you mention, that widespread adoption of it would be just the ticket to drive a round of hardware upgrades.
Democrat delenda est
They should use Javolution open-source XML parsers (pull or sax parsers at http://javolution.org./ They are 3x-5x faster than any other Java xml parsers!
I have noticed another inconsistency that the same users you describe will deny a broken application being caused by Linux itself. But if any app breaks in Windows they are quick to judge Windows itself as being the problem, instead of their incompetence or something caused by another 3rd party app (or even faulty vendor device drivers), or maybe it is just the app is broken. EX: "OpenOffice is soooo slow F%(&%king Windows! All Bill Gates' fault!!11111oneone"
Blame the user, not the software.
The Excel team at Microsoft have always been a bunch of hardcore performance-and-utility fanatics, and the quality of Excel reflects that. In my opinion it's the only component of Microsoft Office that's worth anything, and I dearly wish it was available as a separate program so fat incompetant slobs like Word could be left to scrounge for users on shareware sites.
To maintain performance and compatibility, they refused to get drawn into the COM morass for many years... they interoperated with but didn't depend on COM. At one point they were even using their own compiler. Setting OOO Calc up against Excel is like comparing a donkey to a thoroughbred, and never noticing that the rest of the horses in the stable with the thoroughbred are broken down old screws.
To what extent is this just the proper natural evolution of a large scale application?
Step 1: Functional demo, very lacking in features and stability. This would be StarOffice up through the 5.x series, and the OpenOffice 0.x series.
Step 2: Dramatic increases in stability and completion of all the major technical functions, but with a somewhat clunky or non-intuitive interface. OpenOffice 1.x.
Step 3: More user friendly and natural interface, but performance is not yet up to par.
Step 4: Performance optimization.
Each step is the natural evolution from the prior state. The initial state is an idea, which leads to a functional demo. The functional demo gets poked at by a few outsiders who say, "This might be a good idea, but it doesn't support features X, Y, and Z, and it crashes all the time." That feedback leads to the incorporation of new features and advances in stability. Then a larger group of outsiders uses it and says, "Yeah, this is getting good - it does everything I need it to, but the interface is a little goofy, so I'm sticking with my current solution for now." That feedback leads to user interface improvements. Those improvements lead to a much larger group using the software, and more people using the software full-time, those people say, "Wow, this is really well done, but look at how much (CPU|RAM|disk space|bandwidth) it uses." Which should, inevitably, lead to performance optimization.
That sounds like the natural sequence to me. In fact, that whole process - release, listen, refactor, wait till the end to performance optimize - has always been a big part of successful projects and is now becoming a big part of standardized software development models like those that come under the Agile umbrella. It would be worse if there had been a lot of unnecessary performance optimization that had lead to an unmaintainable code base.
Stop-Prism.org: Opt Out of Surveillance
Yeah, the article didn't mention how much ram the crappy "office startup assistant" takes. I think the real comparison is this: 1) Boot into windows with all unneccessary services off. Load up excel. Check total memory use. 2) Boot into linux with all unneccessary services off. Load up calc. Check total memory use.
OpenOffice, bloated? Suppose we ain't got no Word and go in there and start using OpenOffice anyway? Whatcha gonna do about that? You gonna stop us, Stein? Ha. You're gonna look pretty funny tryin' to eat corn on the cob with no fuckin' teeth.
With Java on, Open Office more often than not kills my poor PC, which is a relatively speedy AMD 1.7ghz with 512MB of RAM. . . to such an extent that it apparently killed my 6 year old Canon.
:)
I only blame it on OO.o because it worked fine earlier in the day when I was printing w/ MSO, but the second I installed OO.o and printed, it went kaput. Le sigh. I miss ol' Canny, she was a good printer.
Seriously though, I don't have the time or the system resources to load OO.o anymore. P2P apps, chat apps, browsers (At least I use Firefox), WinAmp, WordWeb, and the occasional Warcraft 3 session don't need an oversized freeware app sucking their precious RAM. Unless OO.o can offer me comparable quality at a lower price point, I for one will make sure that my money is well spent.
You know, by switching to OSx and just pirating MSO
[Terribly witty statement]
MS Office is slow as dirt on my linux box...see what is the point, come back when I can do
a speed test on linux.
Got Code?
Look at your timings. 30s real time, 3 seconds usertime.
Your first start was totaly HD-bound, while your 2nd start came from your diskcache.
That no magic, you know, and not even knowing such basics just seems like a BIG hint that you shouldnt even try to benchmark.
HI O WISE PRINCE. WHT TOOK U SO DAM LONG?
Isn't that a rather artificial situation? Ok, Microsoft Office may 'cheat' a bit by having some stuff built into Windows, but if that stuff is running when you use Open Office and the real world memory use for Office is bigger, then that matters more than an artificial benchmark-type set-up.
Paul Allen ( Microsoft cofounder ) is the key investor in CNET Networks ( pumped $5 million into the company in 1994 to keep it afloat )
This is a typical "imflame the technophiles" hit/ad creator for ZDNet. They do this time and again and ./ always falls for it. This guys conclusion is based on a small (like 1) test case that he's extrapolating to be an all encompassing fact.
Of course there is some collusion between Intel and Microsoft. But the degree is open for debate. And almost nobody would argue "everything that is good/bad for Intel is good/bad for Microsoft, and vice versa". Their interests are certainly not in perfect harmony.
Keep in mind that the original poster was suggesting that Intel have an interest in making OpenOffice look bad. While Microsoft obviously has a strong interest in making OpenOffice look bad, I fail to see any reason Intel would have a corresponding interest. Simply pointing out that Intel is a part of the Wintel duopoly is a very weak argument.
The Thunderbird email client also takes a loooooong time to start up.
Yeah, I recently cut-n-pasted a howto with lots of graphics from my http client in to OOo. Man, was it chocking just to scroll up/down the page. But you know what? It didn't bother me that much because I figure: (OOo Speed)/co$t goes to infinity in speed per buck while (MS Office speed)/co$t has a lower value.
And time doesn't stand still either. OOo will improve with time.
"Most of that massive speed difference is due to XML being very processor intensive, but Microsoft still handles its own XML files about 7 times faster than OpenOffice.org handles OpenDocument ODS format and uses far less memory than OpenOffice.org."
I don't know if we should blame XML for the bloat.
MS Office has years of optimization in the look & feel -- and speed is part of the "feel" experience.
Opening the same spreadsheet in Windows 2000 with 512MB memory running Office Pro 2003, it took eight seconds to load. According to task manager, excel shows 28,992K. Now I know Excel relies on the MFC so I opened a process viewer. According to that, Excel has 48 DLL's loaded. Um, that seems like a HUGE bit of memory.
The Kai's Semi-Updated Website Thingy
How many people (well average users) actually contribute to the OO even though it's free and open source? Yea sure its open source, so what. I dont care if MS Office is not open source it suits my needs. Oh and besides Office comes free from my school :-).
Its nice to be important but its more important to be nice
Is it bad that I'm 21 years old and think the same thing?
"[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz
"Most of that massive speed difference is due to XML being very processor intensive, but Microsoft still handles its own XML files about 7 times faster than OpenOffice.org handles OpenDocument ODS format and uses far less memory than OpenOffice.org." :-)
Smell a troll here? This aims toward the M$ own XML format being "more efficient" than open XML based format? And using less memory? Bet it is a 10-byte document when opening 7x faster & using much less RAM
I've had to deal with some convoluted MSO doc issues, what with complex corporate templates then being mangled by the occasional bug in doc processing tools. Sometimes simply opening a borked MSO doc would cause the program to crash (mostly seen in Word and Excel). This was the only reason I kept OOo on my XP machine at work, as OOo simply trashed all the careful layout positioning of the original (much better in newer versions) -- but when a doc went belly up, OOo was the only thing we had that could open the doc, and then fix it. Simply opening in OOo and saving would fix whatever the issue was, and we could re-open in MSO. Sure, we had to copy and paste content back into an older version if we were worried about borked layout positioning, but we could get the content, which was the most important thing.
For all the other issues, it looks like the OOo dev team understands MSO's file formats better than MS does. :)
"What in the name of Fats Waller is that?"
"A four-foot prune."
You're right. Mmmmmmmmmm, AbiWord!
Unfortunately no Abi replacement for Excel yet.
On the up side, there's also no analogue of the mind-destroying PowerPlod.
> The best office package I've used is Lotus Smart Suite. I'd be glad to pay a three digit
> sum for a cross-plattform version (Linux/OS X/Win) of that office package.
I'd drop $99 for SmartSuite without thinking. At $199 I'd think a bit, maybe bitch and moan a little and then pay up. But IBM can't bring themselves to invest any money into it and they can't just set it free either. So it languishes in limbo becoming more obsolete year by year until it's value will slide to zero.
Democrat delenda est
Hidden code, you say? Before you go off accusing Microsoft of a Consent Degree violation, perhaps you should be a bit more careful about what exactly you're comparing. It is extremely important when you try to compare "memory usage" on different Operating Systems that you are actually comparing apples to apples. And since you didn't cite the source for your "7.10" and "9.81" numbers above, I doubt you really understand what you're measuring.
If you're using Task Manager, for example, you will by default only see "Mem Usage" which reports the physical memory (i.e., the "working set") consumed by the process. Even though this metric includes both private and shared pages (i.e., shared code and data segments of DLLs are charged to each process here), it does NOT include pages which still reside on disk (either in the executable images, memory-mapped files, or the system pagefile.
Another common memory statistic from Task Manager is "VM Size" (you have to add it to your column view by "View->Select Columns"). "VM Size" tallies private virtual bytes consumed by the process. Private means that this quantity does NOT include shared/shareable pages like DLLs and memory-mapped files. "VM Size" is sometimes smaller than the "Mem Usage" precisely because shared pages aren't counted. This causes a large amount of consternation to those who don't understand what is being reported, because they expect physical memory usage to be smaller. "VM Size" is the equivalent of the process's page file allocation, since shared pages by their nature are already backed up on disk elsewhere.
Another common memory usage metric in Windows can be obtained from Perfmon (perfmon.msc, the Performance MMC snap-in). From this tool, you can view "Virtual Bytes" of each process, which is the amount of reserved virtual memory for the entire process, including shared pages. It is equivalent to "VM Size" from task manager PLUS shared virtual memory.
So, as you can see, it is not altogether obvious what is being reported unless you really understand the details of memory management on the underlying OS. Before comapring application memory usage across platforms, you need to be sure you're using comparable metrics!
I think he forgot to add Windows to that account. MS Office requires Windows, doesn't it?
A better comparison would be:
Now we can start talking.
For a little comparison, I opened an *.rtf file from my documents at random. It's 14kB as rtf. It opened pretty much instantly with OO and Word both (I've used both since logging on). Saved as *.odt and *.doc, my file is now 30kB with Word. And OO, you ask? Still 14kB.
Research is the application of your own bias to something.
Strange women lying in ponds distributing swords is no basis for a system of government.
It could make sense for them to - cutting some bloat could make their state employees more efficient overall.
I tried this recently, just to check on initial memory usage, and fired up Word 2003 and AbiWord v2.4.1, typed in a very small line of text into both (same text), and checked memory usage under Windows - and found AbiWord using slightly less than half the memory that Word 2003 was taking. I've not tried having AbiWord laod up any Word documents or anything like that, yet, but it's certainly worth checking into.
I just timed mine -- Writer took 45 seconds to start up on my gentoo linux box running KDE. It's a 1.2 gig with about 512MB ram. Only other things running are Apache and MySQL. It's about 40 seconds until the splash screen even comes up. The memory stats: VmSize = 155,576, VmRss = 62,760. For some reason, soffice.bin is listed 6 times. I don't know why.
To say the least though, it is frustrating to have to wait nearly a minute to open OO. At least if I open it up soon after I closed it, it opens much faster.
If OOo XML format is quickly becoming the standard format in the open source world.
:D
So, all we need is a small (preferrably command-line) MS Office -> OpenOffice converter which can be called from Abiword and other small alternatives.
Now, who is the pig???
To avoid the user having to install umpteen different libs to get a app to run, a lot of pre-compiled applications on Linux ship with statically linked libs. The libraries are compiled into the code. So there is no ".so" Hell for linux users, but conversely the app is a memory pig. I know FireFox does this as well. StarOffice probably uses it's own instance of Freetype, GTK, etc.
If you DLd and compiled the source yourself ( Say, the crazy Gentoo guys ), I suspect the outcomes may be different.
Part of the problem is libraries mature so fast under linux, and even minor versions can have incompat differences. This is unlike windows, where API changes are static for a lot longer period of time. It's been continually biting us on the butt guys, and even if a distro has a 'standardized' set of libs for one release, well, each distro has a different idea of the 'standard' library version. So again, downloads still need to be statically linked to work on all distros, unless distro specific versions are offered.
Why would someone use a spreadsheet that allows only 16K rows per sheet to load about 250,000 rows, 13 columns per row, of flat ascii data??? (Actually, there are numbers in the data but they are treated as strings in the spreadsheet to further slow things down.) Clearly, a database is called for. But, even if you were bound and determined to use a pickup truck to haul your 600 acres of corn to market, you should at least use a one that allows for a longer bed. George should have put those 250,000+ rows into only one OOo odt sheet.
An aside, why would one save the spreadsheet as an sxc, forcing users to convert to the odt format in order to test OOo, then have sheet settings which resize the row heights and recalculate the spreadsheet before it opens to the user? Because he has to avoid the one sheet solution.
Running with Linux for over 20 years!
how long does it take for msoffice to open an openoffice document ?
Most of that massive speed difference is due to XML being very processor intensive, but Microsoft still handles its own XML files about 7 times faster than OpenOffice.org handles OpenDocument ODS format and uses far less memory than OpenOffice.org
From my experience OO can open Office-formatted files. What is the comparison between OO loading an MS-Office format file and MS-Office loading its own format?
For a PhD dissertation, wouldn't you want to use something like LaTeX?
Even if it does use 50 MB, that joke (8 MB and continually swapping) is still valid... Consider the overall theme of those jokes -- is it unreasonable to think that person might only have 8 MB of ram free when [s]he starts emacs? Surely it would then be continually swapping...
I think the solution to the problem is the forking of the OpenOffice project. Personally, I use only the word processing and the spreadsheet programs. I think that most people only use these two parts of the program...so why not focus on these two? Make them the best. Make each program functional apart from the other. Make each of them lean and mean.
Are you INSANE? It's easy to SAY that, isn't it? Have you _seen_ the code for OpenOffice. My god! *YOU* fork it.
No, better to start from scratch. Maybe borrow some of the code here and there. And yes, that is a huge undertaking -- which is why it hasn't been done. But it would be easier than trying to base anything on OpenOffice..
the core MS-Windows system has high-level libraries used by all Microsoft applications, therefore (in theory) any software developer working in a Microsoft team is not poised to develop whatever was already coined by another. they cooperate
many functions used by many applications (for example MS-Office) are therefore more or less ready-to-go, maybe even already loaded in the memory occupied by the operating system, when you invoke them. this speeds things up
under a free Unix the people developing system and applications rarely talk to each other. the system provides much less high-level functions (above the libc, X) than any modern MS-Windows and the only teams stuffing more factorized high-level code inside it are working on toolkits (KDE, GTK...).
note: one may argue that those libs are user-space things, please note that I use 'system' in the broad sense
this is, at first glance, less efficient than MS-Windows because there is no central authority pumping functions into a single library used by all apps, therefore many applications don't use them. any given desktop will consequently probably use many libraries providing the same services, therefore many free applications come with their own code to do things already done by other ones.
the MS-Windows approach is theoretically wonderful, mainly because less memory is occupied by various codes doing the same thing.
but it leads to various pitfalls. here are some not neglectable ones:
the bloated high-level services provided by MS-Windows are less stable when the machine simultaneously runs many softwares, thanks to awful side effects spawned by heavy multi-layered codes. therefore most users try to run, on a given box, as few services as possible... loosing a good part of the factorization benefits
from my experience the Unix approach is more and more efficient as time passes. it now provides an environment more flexible, easy to maintain and extend, which extracts more useful power from the hardware
it even gains, after a while, the benefit of the 'central library' approach because efficient and stable libraries tend to gain audience among developers, providing a common ground a posteriori (created for a given client code, then evaluated and adopted for others). on this particular matter the efficient way to do thing wins again: don't try to predefine the whole solution, keep it simple, progress slowly, prefer field-proven solutions
this somewhat reminds me of the 'forked childs' classic Unix trick, for a piece of software, to honor requests for each request: run an instance for each request. this means that a bug will probably scrap a request but not block/stall the whole service, which is a very simple and efficient way to achieve crude but often sufficient software-fault tolerance, albeit it is was ressource-hungry. I write was because it is much more less a system hog now, thanks to some low-level enhancements (started w vfork, copy-on-write and such) conceived after this approach
a Unix system developer tend to adopt simple and proven solutions and then fix their issues. a developer of the MS-Windows system overengineers then tries to the make the whole thing run
from my point of view the choice is a no brainer
WebDSign: thrust the Web by trust
I'm using OOo 2.0 and i can load any document within 10 sec. (centrino 1.6 XP SP2) I'v tried also 1MB word doc (80 pages), with OpenOffice and I can open doc format in 4 sec, when I save it as .odt, I can open it also in 4 sec, as xml OpenOffice need 3 min. OK , I don't care. At first, I think they will improve processing xml documents, but with crossplatform OpenOffice I can work with they own format or directly with MS formats.
"What about the source? Ad hominem attacks are a logical fallacy."
I see you're taking philosophy 101 this semester. Be sure to be on the lookout for other strawman, red herring, and ad hominem arguments. No go back to class.
Ninjas don't carry tic tacs
I can not help but remember when I used to mingle with the high-end audio crowd when I read articles and comments such as these. When CD players became affordable in the early 90s nearly every manufacturer hyped the oversampling rate at which their player operated. This supposedly resulted in fewer errors and better sound although the differences were often unnoticable. The technical specifications quickly became a guide as to the overall quality of a piece of equipment, whether it was a receiver or a CD player. For most people this was sufficient and they quickly snapped up commodity bargins through various catalog and retail outlets. High-end enthusiasts approached selecting stereo equipment somewhat differently. An audiophile would often visit a local stereo boutique with a couple of their favorite recordings and spend several hours listening to different pieces of equipment. The technical specs were important but not as important as the overall sound of the equipment. Of course there are arguments regarding whether or not there is any merit to this but that is not the point I am trying to make. I think the way people approach their choice of software is very similar to how they would approach purchasing a stereo. Many folks choose the Microsoft option because it's a name they trust and they can easily be impressed with a whole bevy of statistics they may or may not understand. Folks who opt for open source products such as Open Office tend to look a bit deeper. The number of overall features matter but not so much as whether or not they can use the same software on multiple computers, on different platforms and architectures and whether or not they can easily exchange documents with their colleagues. That last item can be a bit of a sticking point but overall I think the analogy fits. Is Open Office bloated? I guess it depends on how to define bloat. Feature-wise it feels more sparse than Microsoft Office, resource-wise it tips the scales a bit higher and feels more sluggish. I still use it though. I can use it on any computer I own, it allows me to export to PDF much easier and the price doesn't strain my budget. My parents on the other hand are still very new to using computers and the consistency of the interface offered by Microsoft Office suits them better and my mom can purchase a book about Microsoft Office much easier than for Open Office although that is changing. I think the point I'm trying to make is that I think people are going to continue to use Microsoft Office because the "numbers" look better. As Open Office continues to mature I think this will change, especially as people become more budget conscious.
That Open Office is free, where as Microsoft Office costs $300.
I think the most simple explanation is that MS Office is much older than OOo. But this makes me think OOo is even better if they can catch up to MS so fast...
So is it better to spend $X00 on M$-office, or $X00 on RAM to make OO perform better? Hm....
I've been using Abiword and Gnumeric for some time, and I like it much better, especially on my Gentoo system where everything is compiled from source. I guess these pieces of software aren't as featureful yet (they don't have easy integration, and still lack the rest of a productivity suite, but at least when I start them, they, start.
(Of course by that logic, I could get some Free DOS-thing and run WordPerfect and Lotus 123)
A real test would involve 2 different clean installs of Windows: one with Office (and nothing else), and one with OO.o (and no Office having ever been installed) and maybe JVM. Respectively, have Word or Writer auto-launch on boot. Begin typing. Now show me the time from power up to printing a standard business letter that you compose yourself. And total system memory usage (not application only) as a percentage of total available.
What, boot time isn't fair to include? Eliminates the "pre-load" camp's arguments quite handily. Even better, have the system auto-load the specific file for the "file-viewer" benchmark this blogger is doing.
How often do you load a word processor every day? If you are an infrequent user, the overhead is ultimately small because usage is low. If you are a power-user of the office suite than the impact is greatly reduced because it only gets loaded once. Then it gets USED. Where are the usage benchmarks?
Show the numbers for load time as a percentage of your day. Value that time in cash. Weigh that cash against the cost of the two systems. That is assuming you have no OSS or anti-Microsoft agenda = Priceless. THAT's a better benchmark.
This blogger learned about ProcessExplorer. Yippee. He should also learn that a real Office benchmark includes actual usage and creation of content. His benchmark shows the efficacy of the two programs as file viewers only.
I'm thinking about it, therefore I might be.
Or could it be that MS has something built into Windows to hinder Java? I know OO.o uses Java, and that wouldn't exactly be the first time MS used Windows to hurt competitors. . .
www.linuxpenguin.net
...I just started using openoffice for the first time. The word 'internet' gives me a red squiggly. That pisses me off more than bloat.
Does MS compress its XML? OpenOffice's format is XML *inside* a .zip container.
There is a binary XML format called bxml. If OpenOffice were to use BXML for the internal representation of the data, there is reason to believe that parsing XML documents could be significantly faster. In fact, there are performance comparisons using XML from OpenOffice.org's Writer. It looks like a speed up of 4x to 6x would be possible if bxml were to replace xml. This is still an open format and it can be (trivially) converted back to XML. This would be a natural way to have the portablity of XML with an efficient binary data strructure. And it can be done with open source libraries, hopefully with only small changes to the existing code.
Think global, act loco
If you look at the test files, they are HIGHLY redundant, consequently they get zipped extremely effectively .ods is about 3MB but uncompressed xml version is around 192MB.
Based on the memory footprint, Excel is clearly not loading the entire file into ram, or windows is not counting it toward excel. OO on the other hand, not only has to uncompress the file into memory, but hold the entire 192MB file in memory since it is in a compressed form on disk. That comprises the bulk of the difference in memory footprint. Nobody seems to be counting the uncompress time done on the excel file before it is opened either.
This is clearly a pathological test case - however it does lead to a couple interesting strategies: OO could optionally save files uncompressed if the user thinks opening speed is more important the disk space. OO does use more memory and is slower than the Excel app, and this should be addressed for 2.1
The correct response to somebody like George Ou is to say "Thanks for finding this nice test case" and then figuring out whether it really matters, and if so how to fix it.
I produce and proof read quite a lot of technical documentation. The length of time is takes an application to start is nearly meaningless. I'll do that once in an 8-12 hour stint of work.
Metrics along the line of "repaginate a 2000 page document after increasing the generic font size by 1 point including custom headers and footers" would give a better idea of performance loss or gain against Micrsoft's offerings.
Martin Brooks / Slayer99 #linux / UIN 2178117
Besides the fact that it runs on my preferred OS as opposed to MS office, i am pretty satisfied with the speed of all the versions I used. It id bloat for me for sure, but opens whatever I throw at it and usually it runs for 1hours tops a week so I do not care really.
.... also I convert everything into rtf or TEXT and avoid any other format as much as possible..
:) )
:)
I have to admit that i have to deal with very simple tables which I tend to dump into csv, or a mysql table so I can manipulate it without clicking like an idiot
I do not use the presentation maker and the draw at all so I would actually not mind having a thin version (maybe there is one, but I just apt-get openoffice usually at night and I have it in the morning
I run an old machine for my desktop stuff: amd xp2000 with 768m and 2 old nvidia fx-dunnowhat, so my "benchmarks" are not relevant anyway nowadays
You are using 2 DIFFERENT computers. What can you conclude? Different CPU's, different memory speeds, different harddrives, etc. You are comparing apples and oranges. ...
Oh yeah, well I opened a 100K text file on my 3Ghz Linux box in 0.5 sec, but on my 8086 with 256K of memory it took about 45 seconds to load off of the 5.25 floppy disk. See my point?
How does 48 DLL's conclude you to thinking that's a lot of memory? Wouldn't that be a lot of libraries? Run 'ldd' on some of your favorite Linux apps for some side to side comparison.
And just to be helpful in people creating useless statistics, I opened a 540Kb excel sheet in about 4seconds on excel2003, Win2K, 512MB, 1.6Ghz laptop. The time it takes to load from a 10Mbit LAN: 6 seconds. I'll take it home to see how long it takes to load on my desktop with OOo
FREE vs few hundred dollars...
The OOo spreadsheet.ods was 16K, the Excel spreadsheet.xls was 24K in size. The OOo document.odt was 38K, the Word document.doc was 131K in size. In fairness, the documents did contain VB macros that the .odt file did not save. The OOo spreadsheet.pdf was 120 KB , the Excel spreadsheet.pdf was 32KB in size. The OOo document.pdf was 200KB, and the Word document.pdf was 100KB in size. I will check PDF creation on these same documents from my Linux box at home to complete the comparison. My curiosity will then be satisfied.
To me, the expense of archiving data files is of greater interest that the expense of RAM needed to support the software. I must archive documents for many years. Disk space requirements are constantly growing, while the RAM in each PC is reusable.
didn't you see the word "Java" in there?
Oh, but computers are getting faster all the time! Right?
Here's an Idea to speed up OpenOffice deployment.
OK, buy one big server for your network. Install Linux.
Set your use flags.
Install NoMachine http://www.nomachine.com/
Install NoMachine clients on the Windows and Linux workstations.
Create icons on the desktops that will launch the application from the "Big Server" to the clients.
Walah! You have a method for improving the deployment speed of new applications throughout your network from a single place.
Let's look at Gentoo's approach of compiling OpenOffice to see if there are ways of increasing the amount of shared RAM that is used by OpenOffice. Maybe making it less of a static application would help. Then another way to improve execution speed it to introduce a tool called prelink.
Hey, at least we have the application. It is solid and it is free. Now you know ways to deploy it without upgrading all your workstations.
-Joe Baker
I read the blog entry, and this looks like an attempt to report the worst case (corner case) benchmark, for whatever reasons George might find useful. A fuller set of tests and results might make his case that MSOffice is better a little more convincing.
Hard to be convincing about the usefulness of MSOffice over OpenOffice, if you're going to ignore the fact that MSOffice isn't available for some portion of the users, and choose to report a single data point as if it were conclusive.
The Internet has no garbage collection
The Kai's Semi-Updated Website Thingy
http://johnhaller.com/jh/useful_stuff/portable_ope noffice/
You got to love free software, if you don't like it the way it is now. Addapt it to your own needs, or have someone else to addapt it
Your post really is meaningless. Do the test on the same machine and then post, otherwise you are polluting this already hopeless comparison with more bad data. And I still have no idea what your DLL analysis meant.
Bloat vs features.
Openoffice is behind MS Office and is very bloated many times over. I believe its design if you ask anyone who profiled it and knows about operating system internals such as threading and object loading/unloading.
http://saveie6.com/
-My specs-
/proc/cpuinfo
/opt/cxoffice/bin/wine --check --bottle
dotwine --cx-app "C:////Program Files////Microsoft
Office////Office10////EXCEL.EXE"
jcole@jcdebian-p4:~$ uname -a
Linux jcdebian-p4 2.6.12-1-686 #1 Tue Sep 27 12:52:50 JST 2005 i686 GNU/Linux
jcole@jcdebian-p4:~$ grep name
model name : Intel(R) Pentium(R) 4 CPU 2.66GHz
-Time-
jcole@jcdebian-p4:~$ time ooimpress
real 0m6.170s
jcole@jcdebian-p4:~$ time oocalc
real 0m5.537s
jcole@jcdebian-p4:~$ time oomath
real 0m4.928s
jcole@jcdebian-p4:~$ time ooweb
real 0m6.321s
jcole@jcdebian-p4:~$ time oodraw
real 0m6.208s
jcole@jcdebian-p4:~$ time oohtml
real 0m3.792s
jcole@jcdebian-p4:~$ time oowriter
real 0m5.741s
jcole@jcdebian-p4:~$ time ooffice test.sxc
real 0m6.170s
jcole@jcdebian-p4:~$ ll test.sxc
-rw-r--r-- 1 jcole jcole 13196 2005-10-27 11:44 test.sxc
jcole@jcdebian-p4:~$ time abiword
real 0m2.745s
jcole@jcdebian-p4:~$ time gnumeric
real 0m2.343s
jcole@jcdebian-p4:~$ time
real 0m3.514s
-Memory-
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
25721 jcole 16 0 138m 49m 33m S 0.0 4.9 0:03.89 soffice.bin
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
25888 jcole 16 0 1075m 12m 7976 S 0.0 1.2 0:00.89 wine-preloader
Not in terms of bloat, but in terms of slow processing. Firefox's Javascript is HORRIBLY slow in comparison to IE's. I have an intranet site that allows viewing of somewhat large tables of data (up to a few thousand rows), and there's javascript code embedded that allows filtering & sorting of that data. Change a selection in IE and it's done in about 2-3 seconds; in Firefox, the same action can take 45 seconds or more.
I still prefer Firefox, but I use IE if I need to view a large dataset on that page.
Just goes to show, even after functionality is there, there is still a lot of room for improvement in many OSS apps.
I don't usually respond to this sort of thing, but I think you genuinely misunderstood - You quoted my comment, but did you read it? I do not claim any evil/secret/unfair advantage for Microsoft, but simply wish to point out that they have experience in coding within their own paradigm, which works to their advantage.
Kudos to the folks at OpenOffice.org for the work that they have done - it's a steep hill to climb, and they have made a lot of progress, relatively quickly.
And folks, let's not criticize their coding skills unless you are a coder yourself and can do better yourself...If this describes you, then hey, forget the critique and just pitch in!
Using plain ol' text since 1968
I get similar results here. 6 seconds is not so bad to start OpenOffice. So it's 2 to 3 seconds slower, so what? heh.
This is somewhat obvious to me that Excel would run faster, considering it is created by the same company that created the OS it's running on, and it doesn't have to do any VB to java conversions like OO does. I am sure OO would run much faster on JDS and solaris than MS if MS was ported to Solaris. What's the point? I think the 'bloat' numbers are a bit exaggerated (been running OO 2.0 on my XP system here at work for a week, and it runs great). Just now opened a good sized Excel file in OO (charts, formulas, macros, etc) and its using 64 mb right now. With Excel and the same file, 12MB. It's like being a great golfer and creating a golf course and bragging about how you get lower scores than anyone on that course. Big Deal. OO 2.0 is SUCH an improvement over previous versions, I am very pleased with it.
So what you're saying is that bloated software gets un-bloated if you give it more memory to play with?
Why spend more money on hardware if the computer you have is perfectly fine? Don't answer that - the guy above me with the checkbook is already shaking his head NO.
Poor memory management is a sign of poor quality code, or worse, poor planning cycles in development. Better hardware doesn't make your application better.
Indeed. Intel should be pushing OpenOffice, because nothing makes me aware of how much I need to upgrade my processor like starting OpenOffice.
Are you sure? intel would be admitting that its processors are feeble and that you should buy an Opteron or Athlon 64 from AMD. After all, Sun does all its development on 64-bit AMD and UltraSPARC nowadays (with the emphasis on AMD becuae it's cheap, plentiful, and runs cool).
Stick Men
We had a similar discussion regarding Novell and TCP/IP...
TCP/IP was PROVEN to be slower, used more memory and cost more to support.
Score ONE for the market leader.
We revisted the discussion withg VMS vs Unix.
VMS was PROVEN to be faster, more resource efficient and delived a safer support value system.
When they suggested that we should drop our elegant and highly reliable SNA network
for the Internet, we did the benchmarks and showed that security was impossible
to guarantee for critical data when we didn't control the WAN. Don't GO there...
Product are market leaders for a reason... because they sell more than anything
and these "try this/it's free" proponents will never hire enough seasoned resources to
out-code a market leader that has a revenue stream on the order of Billions/year.
It's a simple investment verity! One-Billion downloads at $0 is $0 in revenue.
It's worse than that... who pays for the servers and downloads. Think ROI!
Why we need to revisit this issue again and again is beyond me.
Some people just never learn from history. The author of the article
seems to have some experience in predicting the best use of
IT investments.
I need to get back to my Cobol account app that needs new patches
for our brilliant Web/3270 frontend release.
You slashdotters just need to learn from your wiser, older IT system analysts
before we die off. It's almost too late! There is no such thing as a free lunch...
Lunch doesn't just grow in trees. Your lunch gets cooked in factories like the
think tanks in Redmond and Armonk and Cupertino. Chao.
My post shot up to 4 at first (probably 5), then dropped to -1 and now has oscillated between 1 and 0. (Wouldn't it be cool if moderators could get together, cancel out all the conflicting moddings, and then apply their mod points to other posts?)
I'm just not going to say anymore on this, except that the thing about "running laps around MS" was a general evaluation, not necessarily concerning the speed and storage issues. OO.o is so much easier to use for me, I just love it. That's why I made the incriminating "lap" comment.
Rank my idea: http://www.sinceslicedbread.com/node/531
However, it does do the job and is still free.
That is a fair tradeoff in my book.
---- Booth was a patriot ----
While I agree with your premise that "bloated" and "slow" are always bad, I'm not sure that using a 200+ MB file is representative of how most people use Excel and/or OO. Therefore, if someone found some type of atypical data set that would by it's very nature make either Office or OO perform differently than the average user would expiernce, it's hardly appropriate to use either bloated or slow to describe the results.
A much more representative test would be to use files that are more typical and common. I doubt that the majority of users have such large spreadsheets and documents, at least not for their normal usuage (and if they do, they really should look at using a database instead).
I'm not making a case that OO is better than Office or vice versa. However, using the testing methodology as described, my Ford Focus is slow and bloated because it can't go as fast as a Formula 1 race car. And that would be true, if your criteria was just on the top speed. However, that's not how the typical automobile is used.
So, yes, the Formula 1 is faster and leaner than the Ford Focus, but since the speed limit is far below the top speed of the Formula 1, does it really make a difference? Likewise, Microsoft Office can load more quickly, some huge data file that the average person will never have, but does it really make a difference?
Yes, OSS isn't perfect, however it's strengths (and weaknesses) are not measured in load times and/or memory footprints.
Me here using OO.org for the best part of 3 years for my Open University assignments and have not noticed.
This is a non issue for anybody that looks at the cost of the alternative, not only in monetary terms, but also in terms to access to your own data.
I don't care if it takes a bit longer fo OO.org to do this or that task, at the end I have a document that I am pretty certain I will be able to open and manipulate in a few years time, and I will not have to pay anybody for such privilege if I don;t want to.
Keep putting your data in the hands of the beast, eventually you are going to be deprived of it and will be charged to access it when you more need it.
IANAL but write like a drunk one.
Tired of all the Java FUD.
There's no place like ~/
On my Fedora system, the OOo calc package lists i386 as the architecture, so I'm wondering if SSE/SSE2 floating point is enabled. The old stack-based floating point is slow.
EMACS Makes A Computer Slow
Esc-Meta-Alt-Ctrl-Shift
Subject really says it all. All this open source stuff is for the birds, though I'll admit to raiding a few open source projects for ideas. But damned if I'll use there code. Most of it is C or heavily abused and obfuscated C++. If you want something that's fast and works great, no matter what OS; then you're going to have to pay for it. There's a whole different paradigm when you're writing something to earn a living and writing something for free. You just don't have the same accountability... period.
Is this not exactly what they mean by bloat? I mean if it were the other way around we'd all be bitching about bloated MS software loading all of office up when all I freaking need is excel. It's retarded. Opening up Word, Excel, Etc.. is NOT a fair comparison at all. If all I need to do is 1 thing why should I have them all open? Well with Ope nOffice it sounds like I don't have much of a choice!
Not that this will stop me from using it, but I hope it's something that gets fixed in the future because it really is retarded.
Although.... Correct me if I'm wrong but StarOffice wasn't open source, right? And Open Office is based off StarOffice.. How does this translate into open source software being bloated? I mean it wasn't even fucking open source for most of it's life.
Lets compare Excel to Gnumeric. That's a MUCH better comparison.
My point was more that you're unlikely to increase any understanding of your data by generating said 10,000 point graph, as only about a tenth of them would actually be visible in the output. Similarly, you're probably not going to learn anything useful by looking at a 10,000 row spreadsheet with your eyeballs either. That's too much data to absorb at once, it needs more cooking before it's ready to be displayed in a useful manner.
I'm not making any excuses for OOo. It -is- noticeably slower and it shouldn't be.
I haven't thrown a profiler at it yet to help determine -why- it's slow, but we should.
If you read Gödel, Escher, Bach, you'll read about this idea of a record that cannot be played by a certain record player. If you change the record player to play that record, you can still find another record that the new player can't play.
So, yes, I agree that it's certainly possible to make a spreadsheet that works well with Excel but not with Calc. And I also agree that it may not be a fair test.
But I was more interested in the memory usage for empty documents.
Oh, and I neglected to comment on your last point ("Yes, OSS isn't perfect, however it's strengths (and weaknesses) are not measured in load times and/or memory footprints."). This is the crux of my argument.
FOSS advocates use load times and memory footprints as a means to measure proprietary software, and they do it all the time. And what I'm saying is that since those things matter then, then they also matter now, and the comparison has to be made fairly for all software.
Except for one thing. The OSS world also has software that is not Slow and bloated. This software does not necessarily play well with Microsoft Office and is not necessarily available for non free OS's at this point. So some of us have to deal with Microsoft Office users - using OSS software we can have either light/fast or MS Compatible at the moment - Not Both. On my box (Mepis Linux, 2.5gig Athlon, 1 Gig ram) (I just switched java off - thanks for the Heads up) OOo 2.0 loads in an acceptable time frame. I haven't got any particularly large documents to test the file loading/saving slowness. But I am happy to report that one of the big speed bugbears from OOo 1.1 series is gone - loading charts into Calc. The generally editing is quite snappy too. Would I like to OOo to be faster and use less memory. Yes I would. For the 2.0 release was it more important than having better MS Office compatibility. No it wasn't (not for me anyways).
MacOS 10.4.2 OpenOffice.org_2.0.0rc3_051016_MacosxPPC run Calc:
process real-mem. virtual-mem.
droplet 8.5M 36.5M
X11 0.8M 27.1M
Xquartz 21.8M 168.9M
quartz-wm 3.1M 107.6M
xterm 5.5M 26.9M
sh 0.7M 27.2M
tcsh 1.0M 31.1M
soffice.bin 73.4M 282.1M
All of these processes were started by OOo_Calc. I don't have MSOffice on this machine so no valid comparisons are possible. I observe that OOo is a slug to start from cold, but once up and running seems snappy enough opening, saving docs. I do notice on cow-orkers Macs that MSOffice is running away to talk to the printer every time it opens or saves a doc....
Everyone knows java is a friggin resource PIG. Add a bunch of threads and watch the memory fly! I happen to like java very much, and use it wherever I want cross platform portability. That in itself can be enough of an advantage if that is what you need. Not the perfect solution for everything, but it has very good advantages depending on the situation. I'll gladly add another gig of welfare grade ram to a machine if I need the portability. If your're running windows and openoffice, you have simply shot yourself in the foot twice. Microsoft never wanted java, never wanted to play nice with java, and as far as I'm concerned, still doesn't. Buy some crutches and accept your inevitability.
Join the Slashcott! Feb 10 thru Feb 17!
MS office ver:200.0
Open office Ver 2.0
Thanks for coming out
Gunillablue
I saved this file in .ods and .xls format in OpenOffice 2.0. I opened up the .xls file in Excel (and it does load MUCH faster) and saved it again (again MUCH faster than OO 2.0). File size results: .xls = 52,239,872 (49.8MB) .ods = 4,045,860 (3.85MB)
:)
Sometimes size does matter
What happens if your keyboard has Left, Right, Hyper, Super keys? Do we need to create a new text editor, Lermscash? Or is Emacs sufficiently adaptable that it can be Lermscash, too?
we couldn't even open word documents and liked it!
~~ What's stopping you?
Okay: OSS isn't perfect. I said it.
Nothing is perfect. There are problems with everything. As a rule, I prefer the problems you get with free software, rather than the different problems you get with proprietary.
In the case of OOo, the bloat dates back to StarOffice. I actually tried to use StarOffice 5.x and it was sooo painful on my K6-III/450 computer.
OOo these days is better than StarOffice was but still far from perfect.
I really like both AbiWord and Gnumeric, and I use those by preference. I never use OOo Calc for anything; Gnumeric is all I need. But OOo Writer is much better than AbiWord at opening old Word documents and doing the right thing with them.
Of course my current computers are wayyy faster than my old K6-III and that doesn't hurt either. OOo, despite the bloat, meets the "Good Enough" standard.
By the way, it hass to be said that MS compilers make better code than GCC. If we could recompile FOSS in better compilers it would be better (but OOo would still be bloated, separate problem there). But that's why a comparison of GNOME or KDE vs. Windows 98 made Windows 98 look good on memory issues. (These days, XP burns memory and the FOSS desktops look much better in comparison.)
OOo v2.0.0 uses 15.1Mb (-/+ buffers/cache) RAM when I start it on Linux.
Startup without loading a document was 6.5 seconds first time and 2 seconds once cached. Yeah.. I think I can live with all of that.
Just curious, I've not tried myself.
43 - For those who require slightly more than the answer to life, the universe and everything.
That's why I often prefer to use Abiword. I often don't need anything other than a simple word processor wit basic stuff like headers, highlighting and spelling corrections. for math homework I use OOo, but I am checking into using some advanced app like Texmacs.
My new blog
To be blunt, the guys who wrote the Excel GUI got an "A" in computer science, but the guys who built the calculation engine only got a "C+". To be a truely great spreadsheet, Excel must:
Any engineer who gives me a calculation done in Excel using circular reference calculations had better be prepared to get his butt roasted. I've had 10Mb files modelling a copper smelter that converged to a wrong answer - that's unacceptable given that the same calculation saved as a 1-2-3 file converged to a correct answer in 10 seconds using Lotus 1-2-3.
-AD
Nice Straw-man...
/. crowd says these kinds of things in their arguments is because they READ THEM HERE!!!
People who make speed comparisons are usually making them with regards to some aspect of the OS itself, i.e. some aspect of the linux kernel vs. however we presume MS does it in their latest OS. There are no studies out there that say "Linux is faster than MS" or vice-versa. If there are, they should be ignored or at least heavily scrutinized.
To compare some applications' startup times with arguments about which OS is 'faster' is a classic straw-man argument that I despise seeing. The reason why the
Anyone who thinks less of people who defend Linux should really think about why the Linux community is so defensive in the first place. They have to put up with arguments like this that should be ignored. It's hard to not get upset and defensive when you are presented with one of the most unethical forms of debate tactics ever created.
So far, I haven't seen a single post stating that OpenOffice is faster than MSOffice. All I've seen is people defending their opinion that the difference is not nearly as drastic as the article made it out to seem. In fact, I've seen several posts explaining how to make OO start up faster. It is not obvious that the author of the article has even attempted to try to figure out if there's anything in his control he could have done to level the playing field.
If you want a real argument to debate, here's one: "OO is better than MSOffice because it IS bloated."
If you can provide a non-straw-man argument to support this, whether you agree with it or not, then we forgive you.
Oh no! It *can't* possibly be OpenOffice! Nooo!
...
It's gotta be the processor speed, Windows, or *somehow* related to being Microsoft's fault!
God forbid everything Open Source isn't perfect...
===
Look, gang, step one to correcting a problem is realizing there is one. Realize it, fix it, move on. Improve.
Everyone clamouring for reasons why OpenOffice isn't bloated, I'm not saying you are wrong... I am just going to say this (stiffling urge to say "You are not right" even though it would be funny)
Even *if* it isn't bloated, wouldn't optimizing the speed even further be a benefit either way?
===
Sure, the article is lacking a bit in the specific test methodology department... but just because of that, don't assume that the guy is automatically wrong.
Just my two cents.
MoM++ - A Classic Expanded - [Master of Magic 1.5]
http://mompp.sourceforge.net/
To add insult to injury... Cross Over Office Wine runs MS Office under linux faster than OOo runs under linux natively! It is insaine! That is why I have quit using OOo and I now run MS Office via wine.
There is no reason to run OOo except for the fact that you either:
Don't want to pay for the MS Office + CWO Wine
or
You don't want to pirate MS Office + CWO Wine
Excel is the piece of Office that I just can't quit using yet. (Consequently, I do like OO Writer better than MS Word. Especially when it comes to nested tables.)
.xls:
Excel allows for cool tricks like pasting the following into a text file and naming it
testtest2
test3test4
If you try to open that same xls in openoffice it opens it in writer.
The man who trades freedom for security does not deserve nor will he ever receive either. - Benjamin Franklin
It's Microsoft software which is bloated and buggy. Everyone knows that. Always was true, always will be true. Microsoft couldn't code their way out of a paper bag. I use OO all the time, and I know that it's faster than Office...or that it doesn't matter..or that it's because Microsoft screwed Netscape, or it's because I don't understand Open Source, or something....
I'm a software visionary. I don't code.
Two reasons near the top are that Windows is slower and more bloated. These reasons are sited often and are part of the OSS mantra.
I would say this *was* part of the OSS mantra, but was quiety dropped for obvious reasons when OSS desktops got to the same level of functionality as Windows.
To compound matters, they couldn't agree on API standards, essentially forcing users to keep three or four entirely unique frameworks in core to accomplish the same objective as Win32. Thus bloat went from an advocacy point to something that is nearly an order of magnitude worse on the OSS desktop.
The current OSS mantra is "security", but once again it looks like this talking point might turn around and bite them in the ass.
Whenever I hear the word 'Innovation', I reach for my pistol.
Because spending money on hardware is cheaper than spending money on software.
Yes, SO has been around a long time, going back to the heyday of OS/2 and German corporate needs for an office/productivity software solution.
Nevertheless, there is no question but that M$ has about a 1000-to-1 advantage in "man hours" spent on its Office over OO.
Although open source development should alter this ratio substantially over time.
It's time for you to have egg on your face, admit it, and take it like an adult. And then the next thing you need to do is stop wasting your time and fix the problem.
What egg? Gnumeric and Kword run circles around both OO and M$ Office. As a free software fan, I have my choice of applications. Unlike 20 years ago, that's not the case on Microsoft platforms. The primary reason to run OO is to open Microsoft's horrid and bloated file formats with an editor that has good html and pdf export. When I want to write a paper or manipulate data the free software world has more choices that work better than Bill Gate's best wet dream. The problem is solved because it never existed.
I call bullshit on ZDNet. That Wintel rag never gets free software stories right and often gets them wrong deliberately. It's not worth reading and I could care less what gets published there. OO may be big and bloated next to other software but Microsoft is the prize hog and always will be.
In this case, it goes against personal experience. I can and do run OO on systems with resources Microsoft's latest, the now five year old XP, won't even install on. When I need a slide show, I pop open OO presenter on ... a Pentium 2 with less than 256MB of RAM. Try that with M$ crap-ola. Sure, you might be able to create an 80MB monster piece with software that Microsoft has abandon support for. Good luck getting it off that machine on a network, ha ha. Will your new copy of Office render it correctly?
An extreme example of fat new software on skinny old hardware was posted onto my LUG recently. Check out OO running on a 133MHz Pentium laptop with 70MB of RAM:
Holy Shit! That's crazy. But far from 200MB for OO alone, the combined six or seven big applications took 120MB of swap. The nutcase ran OO, Abiword, Kword, Kontact, Konqueror, GIMP and other software at the same time on separate virtual desktops. XP would be a fragging, blue screened disaster if someone tried to run M$ Office, Outlook, Photoshop and IE all at the same time, say nothing of trying to load up a few other extras.
When someone does that with XP or Vista and M$ Office, I'll believe that they are no less bloated than OO and Linux. Right now, I believe, XP won't install on less than a P3.
Friends don't help friends install M$ junk.
Given that: I have to admit guilt. Does anybody know of a really good intro to Base (oo.o's database). I need database functions, but every time I try to get started, I end up floundering.
If anybody knows where I can find an excellent book/ tutorial/ whatever so I can learn Base, I promise to stop making bloated spreadsheets. (MS Access tutorials are, however, out of the question.)
Thanks very much, any who respond helpfully.
hanzie.
********* sig: If you don't like the law, get filthy stinking rich, and buy a better one.
I've got a finance spreadsheet with about a dozen graphs, each with 30-60 points. Excel can recalculate them all almost instantly (< 1 second). OOo takes about 20 seconds. That's 20 seconds every time I hit Enter. Argh.
Who the fsck modded this "insightful"?
with a proprietary code base
Huh? Go get the source. Proprietary? To whom?
an open-sourced proprietary product.
What? Perhaps if you type in a less MS shill tone I could see what in the heck you are after. OOo is open source, there is no propriety to it, grab the source, fork it all you want. Is SUN a major contributer? Yup. Is Star Office OS? Nope. Does OOo get all the cool stuff from Star Office as OS? Yup.
Really - what is your beef with the licence? OOo *IS* OS ... there is no "Proprietary" to it.
Sera
Slashdot, where armchair scientists get shouted down and armchair theologians get modded up.
This is one area where Open Source has its weakness.
Cutting down and optimizing existing code is not nearly as glorious as adding new features.
Exactly how did you arrive at that conclusion, by pulling it out of your butt after reading this one article? There is absolutely no evidence to indicate that open source promotes feature-creep and bloat. In fact the opposite could be true.
Try to compare OO.o to previous versions of itself rather than just MS Office. On the same hardware you'll find OO.o starts faster and consumes less resources than previous versions. I've NEVER seen the same trend in MS Office or ANY Microsoft products--in fact major upgrades of ALL MS software have consumed more hard drive space and had the same or higher recommended system requirements. Yes, OO.o probably does still not compare well for efficiency compared to MS Office, but with each new release the gap closes. I'm betting that the next version of OO.o will be a bit more efficient, while the next release of MS Office will be less efficient.
Your assumption that adding features is the most "glorious" task and thus receives the most attention from F/OSS develoers is also somewhat flawed. Efficiency and clever solutions tend to be the greatest source of pride in terms of engineering, and I find that open source developers usually take a more engineering-like approach to their creations than commercial developers, where marketing is the biggest driving force. It seems to me that the FOSS culture is influenced by the open culture demonstrated by early PC hardware hackers like the original homebrew club. Anyone could (and did) make their creations do more. The ones who did more with less were the ones who had all the glory. Steve Wozniak's Apple I and II designs didn't get accolades because they had the most features--even in the late 70s you could get Altair/S100 bus video cards to provide "modern" I/O, colour graphics, sound, etc. Woz was heralded for providing those desirable features in elegant, very clever and hackable designs that used far less components and cost significantly less than competing designs.
As FOSS projects become more "free" it seems they become more efficient and more modular. The Mozilla foundation is a good example--they inherited a bloated, monolithic and unmaintainable closed-source project in Netscape Communicator. It didn't take the artitechts of Mozilla long to decide to scrap it all and make the code more modular and maintainalbe...and evenually that thinking extended from the architeture to the end applications, when a set of more lightweight applications (Firefox, Thunderbird, Sunbird) has taken the spotlight over the big, feature-laden traditional Mozilla suite.
The OO.o project has a history similar to the Mozilla project, but the evolution of the project has folowed a somewhat different path. The OO.o project has roots in a closed-source office suite from Germany. Sun acquired it and subsequently opened the project. I personally dislike the architecture of OO.o as it is too monolithic for my tastes. My opinion may be biased by my first impressions of the first releases of OO.o...if left a bad taste in my mouth like when I tried to used Microsoft Works (you know, the taste you get when you throw up in your mouth a little bit...). I still hold out hope that those involved in the development of OO.o make a push towards "breaking things up" so that Writer, Calc, Impress, Database can be downloaded and used independently of each other like Firefox and Thunderbird. I think that because Sun is the sponsoring organisation and has such an influence in steeering the project that this will be tough though. I think the evapouration of Netscape corporation was really the best thing to happen to Mozilla--it has meant that the foundation has steered the developemnt of the Netscape product, where with OO.o it still seems to be the wrong way around--like StarOffice steers OO.o where Sun wants too much.
In any case, there is another benefit to F/OSS:
~~~~
:-)
From: Guy de'Geek
Newsgroups: comp.office.app
Subject: What would you like to see most in openoffice?
Summary: small poll for my new office suite
Date: 25 Oct 2005 20:57:08 GMT
Hello everybody out there using OpenOffice -
I'm doing a (free) office suite (just a hobby, won't be big and
professional like OOo) for 586(686) stones. This has been brewing
since april, and is starting to get ready. I'd like any feedback on
things people like/dislike in openoffice, as my suite resembles it somewhat
(same layout of the GUI (due to practical reasons) among other things).
I've currently done numberscruncher and wordscruncher apps, and things seem to work.
This implies that I'll get something practical within a few months, and
I'd like to know what features most people would want. Any suggestions
are welcome, but I won't promise I'll implement them
PS. Yes - it's free of any openoffice code, and it is fast,
multi-threaded and not greedy to resources. It has descent charting too.
~~~~~
So there is hope...
I had a user with a corrupt Excel spreadsheet. She wanted me to dig up a tape backup from March to restore. Instead I opened it in OpenOffice, and saved it back to Excel format, and voila, it mirculously opened in Excel again. So, in this instance, at least, OOo was much faster. :)
I'm not sure how valid memory usage for empty documents really is. For example, let's say that there are two identical programs, coded exactly the same way except that one of the two programs allocates a lot of buffer space up front to keep from having to do it on the fly (since memory allocation is usually cpu intensive). Which of the two programs is the better one? Of course, the answer might be different if one is trying to run on 128MB vs 2GB.
.Net with the OS, then we'll here the same kind of arguments -- "Look how much memory a java app takes, when C# uses next to none!"
Don't get me wrong. OO has lots of room for improvement, but I'm not sure that empty document memory usage is a valid measure. For one thing. All of those Windows DLLs that Office requires but are part of the OS don't get counted in the memory footprint. Now it is true that they are part of the OS but technically, they should be counted. OO doesn't have that luxury -- all of it's memory footprint is displayed, because it can't rely on the Windows DLLs and remain multi-platform. If one day, Microsoft is successful in integrating
All of that said, OO does suffer from having a monolithic architecture. You shouldn't have to have Writer and Impress loaded just to use Calc.
True. But you can't by Excel "OEM" (at least I've never seen it). An OEM copy of the basic MS Office Suite (Excel, Word, Outlook) from Dell is ~ $150. From your link, Excel itself is $229. I think I'll take the suite.
I don't think it's just FOSS advocates that use load times and memory footprints but instead most people do. It's something that on the surface appears to be objective, but in reality is not. Businesses don't care about either. When they evaluate applications, it's based on functionality, productivity, cost, etc. Memory footprints only factor in if additional memory is needed, thus driving up the cost. The only people that really care about load times and memory footprints are the technical people. Average Joe user, isn't even aware of it, or if he is, doesn't understand it.
Case in point. Most new Linux users get all concerned when they check memory usage and see that they are near maximum. They don't understand that the OS is using all available RAM for it's own processes until something in user space requires it.
FOSS may report or quote things like load times and memory footprints, but if so, it's only because people expect them to. FOSS never even mentions any of those kinds of things when describing what FOSS actually is.
In reality, comparing load times and memory footprints is about as meaningful as using MIPS to compare mainframe systems. What's the joke about MIPS? MIPS=Meaningless Indicator of Processing Speed. Likewise, comparing memory footprints and load times is meaningless for the average user.
Why use a db engine written in JAVA when there's already SQLite?
Are the "very same people" saying both things? I must admit I don't keep a database of what everybody said, so if you could post an example of a single person saying both contradictory things then that would be super.
You, sir, ought to get a prize for showing exceptional idiocy even by /. standards.
.Net with the OS, then we'll here the same kind of arguments -- "Look how much memory a java app takes, when C# uses next to none!"
All of those Windows DLLs that Office requires but are part of the OS don't get counted in the memory footprint.
Wrong. Wrong. Wrong. Which DLLs are these? GDI? User? AdvApi? Kernel? Here's a clue: OO uses them as well. So does every other Windows app (that includes java.exe and javaw.exe)
Now it is true that they are part of the OS but technically, they should be counted.
They aren't counted in the working set, but they are counted in the virtual size (which is a measure of how much of a process' address space is used up). However, virtual size (for the purposes of this discussion) doesn't matter because its amortized across apps. The OS' shell (explorer.exe) already loads most of these DLLs. So any apps that links against these DLLs will 'run faster' because most of its stuff is already loaded.
Unless of course they insist on loading LOTS of their own dinky libraries at startup time. Like Seamonkey pre 1.7. Or OO.o. One reason Firefox got popular was because its developers actually had a clue about writing good Windows programs and took advantage of almost every trick in the book (I use XP and Ubuntu Hoary and Firefox always starts faster on XP).
Translation: code targeting a particular OS' features and environment will always run faster than generic crossplatform code. Big surprise.
If one day, Microsoft is successful in integrating
Wtf? Talk about clueless paranoia. Please. Someone give a the parent a Purple Brain for stupidity.
Go somewhere random
Yes, Excel does run slightly faster than Calc--who cares? It is easer to use. At 2'5 GHz you don't notice. Personally, I only use Excel for training to use Calc better (it works) since there is lots more information on Excel. By the way, I have found that Word 2003 as part of the full office suite is the most unstable word processor on the face of the planet--it has destroyed it's own documents for me. do you want to type 27 pages all over again because Word had a problem while you had the document open??? NO,I didn't think so....
John W....
The only people that really care about load times and memory footprints are the technical people. Average Joe user, isn't even aware of it, or if he is, doesn't understand it.
Most people won't care about memory footprint (so long as it doesn't cause swapping, a big if), but every person notices slowness. There is a reason that UI guidelines suggest responding in 0.1seconds to user's actions, and that should ideally apply to loading programs as well.
For every expert, there is an equal and opposite expert. - Arthur C. Clarke
With OpenOffice (OOo) being a Solaris-friendly application (both are made by Sun), we can soon open those Office documents a lot faster, and save a Citrix license, an Office license, and a bunch of heavy PC servers running Citrix. Native applications rule!
But the story does not end there. Once all Sun users use OOo, eventually someone will break a document because of incompatibilities between OOo and MSO in handling the Office format. Therefor we are now already looking into making (OASIS) OpenDocument (ODF) our default format for certain development documentation that is primarily authored by Sun users. IT must then roll out OOo on all PCs to be able to view/review/edit ODF (MS refuses to add support for ODF).
After that it's a small step to a full switch to ODF, especially since the XML is totally open and preferable over MSO-12 (our Sun users must also view the XML). By then the beancounter will come in for the kill: why spend MSO license money for 5000+ employees when you can do with a free and 99% compatible alternative, that even kills the necessity for Acrobat Elements (PDF generator for 100+ user companies) and a lot of Citrix licenses and hardware.
The trend in IT is 'cutting cost'. So we will probably end up with the cheapest hardware (PC) with the cheapest OS (Linux), with the cheapest office suite (OOo), browser (Firefox), email client (Thunderbird), HTML editor (Nvu), graphics suite (GIMP), graphics conversion (ImageMagick), and so on.
Guess what: most of that software already runs in our company on Solaris and on WinXP today. Switching to Linux PCs is a breeze because users are already got used to the applications over the past years one by one. No costly retraining. Some users may not even notice the difference between SuSE Linux and WinXP, other than that the applications are now grouped together by type in the Start menu, rather than by manufacturer.
I don't see the problem. Yes it takes a few seconds to load a typical file I use, but I can't type fast enough to race ahead of it. When I'm typing as fast as I type (which is pretty fast) my system CPU meter in gkrellm barely moves. OO may be "slow", but the human driving it is slower and is the limiting factor for how fast text can be entered.
OO for me is free. It works. It was ahead of Microsoft Excel for putting formatting inside spreadsheet cells, so for drawing sound cue sheets for theatre with formatted instructions for the operator it wins hands down. I couldn't do things like make "Be sure to patch to group 2" bold in Microsoft Office.
I have a friend who's been on an old MS Office and is having difficulty moving her documents to new versions. Open Office is a winner here! I'll have to see how the migration goes.
I'm running on a 600MHz Mini-ITX M6000 with 512M RAM. I don't know how Windows XP's memory management compares with Linux. Older versions of Windows were pretty poor. I'm running the Debian OpenOffice packages with the Gtk/Gnome support so should be getting some help from shared libraries. I remember the old Debian OpenOffice installer used to prelink, though I don't think this one does. Program load time is not too bad though.
If it can be disabled without losing functionality, what's it there for?
(I can't find the Java option in my OOo 1.1.3)
My Hyundia Excel does not out perform my neighbours ferrari. Yes it is true but what do you expect when you compare the price
I realize that it didn't get moderated as such, but *I* thought it was a funny post... :-)
last time I used MSWord willingly (true, it was in '99, on Win95 and it was version 6), it crashed after it mangled my file and *saved* it. I could not open that file again using Word or another text processor, and had to edit it in MSEdit to delete the binary crap and unshuffle the text ... managed to recover less than half ... OOffice still has to beat this ...
If I only wanted to process text, I would use vim or wordpad. Maybe you only use your word processor for 9th grade English assignments, but most normal people use them for things like research papers and reports and such. These often have more figures and equations than text.
Ok I just did an exmap test on OOo Writer - I am getting ~50mb of effective memory usage. That is still the heaviest thing on my system apart from (x.org)...
:p
I haven't actually got any document open (its a blank page) and I have disabled Java. I would love to test Microsoft Office but I have neither the money to waste nor a system to run it on
The special training at corporate headquarters is probably one of the reasons there is sometimes a hiatus and it'll go a few days without a peep in defense of M$. They'll also attack, usually with logical fallacies (e.g. ad hominem), any criticism or even critique of products or initiatives that are being launched. (e.g. right now MS SQL.) Read carefully the next attacks from MS fanbois and see that they usually change the topic or go into name calling.
Anyway, it's not a surprise to see them go after OOo and less so for OpenDocument. Both cut into their MS Office revenue. OpenDocument cuts off the lock-in at the file format level, removing dependence on MS for continued use of the documents.
Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
hum, let me see....... In my desktop I can get
$0 OpenOffice.org loading slower,doin anything Office does,supporting OpenDocument (my files will be good FOREVER)
$250-300 Office loading faster, supporting closed-formats (when I'll decide to change office, I'll have to pray MS...)
hum... difficult choice.... but I think I'll use all those bucks in another way:
$50 donation to openoffice.org
$150 new cpu/motherboard to my old system. Now not only OpenOffice is goin nearly as fast as Office was goin on the older
system, but all other apps are faster......
$50-100 Cinema,DVD, meeting girlfriend.....