Re: [dev] OLE conversion sun build vs. the rest of the world [ Was RE: [dev] .Doc importer performance ]
Can I tell OO not to convert OLE objects when I use loadComponentFromURL ( e.g. case by case) and is there a way to tell it to never convert the object? My application needs to load documents very fast, and is fine with OLE objects as bitmaps. Laurent. On 3/27/07, Gregoire Gentil [EMAIL PROTECTED] wrote: Mikhail (and others), Actually, you're right. Sun build has the OLE conversion unchecked. Just to summarize and close this thread (perhaps it could be useful to somebody else in the future): We noticed huge difference of performance of the import of a big Word document between the Sun build and all other Oo builds (15 seconds vs. 2 minutes). The problem was that this document had some enbeded OLE objects and by default Sun binaries doesn't convert OLE objects (open as an image upon double click) while all other Oo binaries like Novell, Ubuntu, or Gentoo, does convert the object (open as a spreadsheet upong double click). Thanks to all who helped to clear up this mistery, Gregoire -Original Message- From: Mikhail Voitenko [mailto:[EMAIL PROTECTED] Sent: Monday, March 26, 2007 6:58 AM To: dev@openoffice.org Subject: Re: [dev] OLE conversion sun build vs. the rest of the world [ Was RE: [dev] .Doc importer performance ] Hi Gregoire, Actually all the optimizations for the OLE object loading are commited to the OOo cvs tree. So the behavior should be just the same, although I do not know the details about how the other binaries are built. By the way, had all the office builds the same version OOo2.1? Can it be that a different version was built to be compared with OOo2.1? How many time does it take to load the document without conversions? I am asking, because the mentioned difference looks pretty like as if the conversion was not used in the fast case. If it was activated, could you please check whether all of the imported embedded objects are correctly converted ( to do this, please activate the objects, the normal internal OOo embedded objecs should be activated inplace in this case usually ). Regards, Mikhail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [dev] OLE conversion sun build vs. the rest of the world [ Was RE: [dev] .Doc importer performance ]
Mikhail (and others), Actually, you're right. Sun build has the OLE conversion unchecked. Just to summarize and close this thread (perhaps it could be useful to somebody else in the future): We noticed huge difference of performance of the import of a big Word document between the Sun build and all other Oo builds (15 seconds vs. 2 minutes). The problem was that this document had some enbeded OLE objects and by default Sun binaries doesn't convert OLE objects (open as an image upon double click) while all other Oo binaries like Novell, Ubuntu, or Gentoo, does convert the object (open as a spreadsheet upong double click). Thanks to all who helped to clear up this mistery, Gregoire -Original Message- From: Mikhail Voitenko [mailto:[EMAIL PROTECTED] Sent: Monday, March 26, 2007 6:58 AM To: dev@openoffice.org Subject: Re: [dev] OLE conversion sun build vs. the rest of the world [ Was RE: [dev] .Doc importer performance ] Hi Gregoire, Actually all the optimizations for the OLE object loading are commited to the OOo cvs tree. So the behavior should be just the same, although I do not know the details about how the other binaries are built. By the way, had all the office builds the same version OOo2.1? Can it be that a different version was built to be compared with OOo2.1? How many time does it take to load the document without conversions? I am asking, because the mentioned difference looks pretty like as if the conversion was not used in the fast case. If it was activated, could you please check whether all of the imported embedded objects are correctly converted ( to do this, please activate the objects, the normal internal OOo embedded objecs should be activated inplace in this case usually ). Regards, Mikhail. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] OLE conversion sun build vs. the rest of the world [ Was RE: [dev] .Doc importer performance ]
Gregoire Gentil wrote: Hello, Hi there! We are are integrating OpenOffice 2.1 in our own Linux distribution. We have a problem with the OLE-load/save conversion of the importer. We have found a huge performance gap between the Sun binaries and any other compiled binaries (Gentoo, Novell, Ubuntu...) when importing a complex word document with some OLE objects. When the OLE-LOAD CONVERSION is checked, 2.1 Sun binaries takes 10 seconds to open the doc while any other compiled binaries (Gentoo, Novell, Ubuntu...) takes two to three minutes to open the same document. If the OLE-load conversion is unchecked, performance is identical. Obviously, if there is no embeded OLE object, situation is identical for all binaries. Does anybody have an idea what could explain this huge performance gap? Just a wild guess: What about that makro conversion stuff that hasn´t yet made it into a mainstream milestone but might eventually be included as patch through ooo-build build environment, maybe that´s dragging down performance drastically. Is there any patch for the OLE-load/save conversion that is in the Sun build and not available in any other distribution? I believe it could also be the other way round that there is a patch in the other distributions that is not (yet) in the Sun build ;-) Many thanks by advance. Best regards, Gregoire Kind regards, Bernd Eilers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] OLE conversion sun build vs. the rest of the world [ Was RE: [dev] .Doc importer performance ]
Hi Gregoire, Actually all the optimizations for the OLE object loading are commited to the OOo cvs tree. So the behavior should be just the same, although I do not know the details about how the other binaries are built. By the way, had all the office builds the same version OOo2.1? Can it be that a different version was built to be compared with OOo2.1? How many time does it take to load the document without conversions? I am asking, because the mentioned difference looks pretty like as if the conversion was not used in the fast case. If it was activated, could you please check whether all of the imported embedded objects are correctly converted ( to do this, please activate the objects, the normal internal OOo embedded objecs should be activated inplace in this case usually ). Regards, Mikhail. Gregoire Gentil wrote: Hello, We are are integrating OpenOffice 2.1 in our own Linux distribution. We have a problem with the OLE-load/save conversion of the importer. We have found a huge performance gap between the Sun binaries and any other compiled binaries (Gentoo, Novell, Ubuntu...) when importing a complex word document with some OLE objects. When the OLE-LOAD CONVERSION is checked, 2.1 Sun binaries takes 10 seconds to open the doc while any other compiled binaries (Gentoo, Novell, Ubuntu...) takes two to three minutes to open the same document. If the OLE-load conversion is unchecked, performance is identical. Obviously, if there is no embeded OLE object, situation is identical for all binaries. Does anybody have an idea what could explain this huge performance gap? Is there any patch for the OLE-load/save conversion that is in the Sun build and not available in any other distribution? Many thanks by advance. Best regards, Gregoire -Original Message- From: Jens-Heiner Rechtien [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 20, 2007 4:13 AM To: dev@openoffice.org Subject: Re: [dev] .Doc importer performance Gregoire Gentil wrote: Hello, When I big import a Microsoft Word .doc document with the Sun binaries ooo 2.1, the document opens in 20s. When I import it with my own compilation of ooo (Gentoo, gcc 4.1, a set of coherent/optimized flags), it takes more then two minutes. Can anyone tell me if there is any specific optimization of the importer in the Sun binaries and how to reproduce them? The optimization flags for our (Sun) build can be found in solenv/inc/unxlngi6.mk. The flags for the doc importer are the same as for the rest of the build (sometimes someone uses local flags via ENVCFLAGS, please check the makefile.mk's of of the import code) Maybe gcc-4.1 mis-optimizes something? Heiner - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
