Welcome to NeoOffice developer notes and announcements
NeoOffice
Developer notes and announcements
 
 

This website is an archive and is no longer active
NeoOffice announcements have moved to the NeoOffice News website


Support
· Forums
· NeoOffice Support
· NeoWiki


Announcements
· Twitter @NeoOffice


Downloads
· Download NeoOffice


  
NeoOffice :: View topic - OpenOffice vs. Neo/J startup times
OpenOffice vs. Neo/J startup times
 
   NeoOffice Forum Index -> NeoOffice Testing
View previous topic :: View next topic  
Author Message
jimlaurent
Captain


Joined: Jun 23, 2003
Posts: 55

PostPosted: Sat Sep 13, 2003 10:47 am    Post subject: OpenOffice vs. Neo/J startup times

For pure entertainment value, I decided to see which was slower on my iMac DV 400 with 768 RAM. I have 10.2.6 and the Java 1.4.1 update 1 Java patch

Neo/J 1 min 24 seconds startup
OpenOffice 1.0.3 52 seconds startup.


This was suprising when you consider the OOO actually has to go through "StartOpenOffice", X11 and then OpenOffice.

I also find the menu pulldowns on OOO to be much faster.

I have noticed in Neo/J that sometimes when pulling a menu down and clicking on the menu item, I have to click it twice to get a response. I don't know if this is a performance thing or a missed event thing.

Anyway, I'm looking forward to the drawing patches for lines and objects.

Great work. Get this project a little farther along and I would plan to endorse it on the Mac users mail alias inside of Sun to get you more exposure, testing and feedback.

Certainly at that point I would rather see an updated single downloadable installer rather than download the installer and manually drop a few different patch files in place.

Jim Laurent
Back to top
pluby
The Architect
The Architect


Joined: Jun 16, 2003
Posts: 11949

PostPosted: Sat Sep 13, 2003 11:33 am    Post subject: Re: OpenOffice vs. Neo/J startup times

jimlaurent wrote:
For pure entertainment value, I decided to see which was slower on my iMac DV 400 with 768 RAM. I have 10.2.6 and the Java 1.4.1 update 1 Java patch

Neo/J 1 min 24 seconds startup
OpenOffice 1.0.3 52 seconds startup.


This was suprising when you consider the OOO actually has to go through "StartOpenOffice", X11 and then OpenOffice.

I also find the menu pulldowns on OOO to be much faster.


There is some more bad news. When I fixed the line drawing problems that you posted, I found that there was a much bigger bug: OOo wants to draw many lines in XOR mode and Java's line drawing does not support XOR drawing. So, when I implemented XOR line drawing, I noticed that documents with lots of lines (like the sample document that you sent me) take almost 10 seconds to iniitially paint! Most text documents aren't affected by the XOR fix, but documents that have grids in their backgrounds are noticeably slower.

Of course, my XOR implementation is very inefficient (lots of drawing lines to an off-screen image, merging the off-screen image with the pixels on the screen, and then painting the merged image to the screen) so there is lots of room for improvement.

Overall, for NeoOffice/J I have been using the approach of "make it work reliably, then make it fast". So, once I have all of the core features working in NeoOffice/J (I still need to handle high-resolution priniting, implement copy and paste, and upgrade to OOo 1.1), the main development focus for NeoOffice/J will be optimizing the really ineffiicient drawing code.

jimlaurent wrote:
I have noticed in Neo/J that sometimes when pulling a menu down and clicking on the menu item, I have to click it twice to get a response. I don't know if this is a performance thing or a missed event thing.


I noticed that too and I already fixed it. It will be in the next printtest patch.

Patrick
Back to top
Apricot
Pure-blooded Human


Joined: May 31, 2003
Posts: 38

PostPosted: Sun Sep 14, 2003 12:50 pm    Post subject:

Quote:
Overall, for NeoOffice/J I have been using the approach of "make it work reliably, then make it fast". So, once I have all of the core features working in NeoOffice/J (I still need to handle high-resolution priniting, implement copy and paste, and upgrade to OOo 1.1), the main development focus for NeoOffice/J will be optimizing the really ineffiicient drawing code.


Very wise approach. However, as one humble voice among many, I hope you will bump the draw optimizing up higher in priority than going to OOo 1.1.

Times like this I wish I knew Java...

- Ap
Back to top
Display posts from previous:   
   NeoOffice Forum Index -> NeoOffice Testing All times are GMT - 7 Hours
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum

Powered by phpBB © 2001, 2005 phpBB Group

All logos and trademarks in this site are property of their respective owner. The comments are property of their posters, all the rest © Planamesa Inc.
NeoOffice is a registered trademark of Planamesa Inc. and may not be used without permission.
PHP-Nuke Copyright © 2005 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.