NeoOffice 2.0 Alpha PowerPC memory usage

[pluby]

FYI. Fabrizio filed bug 1418 regarding high memory usage in Neo 2.0 Alpha PowerPC. While Patch 2 fixed the high memory usage for large text documents, I am still working on reducing memory usage for large images.

I have started posting test patches with some very dramatic reductions in memory usage for images in that bug. The code may or not work well, but if you have large image documents, I invite testers to try out any test patches that I post in that bug and add any breakages that you see between the test patches and Patch 2.

Patrick

[pluby]

FYI. I posted a new test patch in bug 1418. The latest includes optimized printing of images. My optimization now bypasses Java entirely when printing images and, instead, prints directly using Mac OS X's native APIs.

Please try this code out if you can as I'd like to include this code in new official Neo 2.0 Alpha PowerPC patch before the EAP drops to US$10 next week.

Thanks,

Patrick

[toonetown]

Are these patches against the EAP patch release, or do you have to apply them to CVS? (Basically, I'm building from CVS HEAD - do I need to just update to get these for testing?)

[pluby]

If you are building from CVS HEAD, applying the patch should work since I build the patch from my HEAD build. Also, since anoncvs can be up to 12 hours behind my commits, you may or may not see my commits immediately.

Also, note that you should remember the following:

1. Always do a "cvs update -d" as the "-d" is needed to pick up any new directories that I have added.

2. When doing a cvs update, looking for files with a "C" status. This indicates that I have added a new file where previously I softlinked to the OOo code. You will need to delete any such softlinks and cvs update again.

3. The Neo build is designed around preventing rebuilding so don't expect the Neo portions of the code to automatically rebuild after a cvs update. Instead, you need to manually force rebuilding of any Neo modules that have updated or new files by deleting the module's build.neo_<module>_patch file before you invoke make.

Failure to do any of these will give you a tweaked or corrupted build.

Patrick

[pluby]

Has anyone noticed any difference with the test patch? Note that this was a major change and I would really like to know if there are any problems before I spin the next early access patch and binary this weekend.

Patrick

[OPENSTEP]

I'll rebuild tonight. I've got mixtures of graphics heavy and text heavy spec documents of mine with me (200pg+) and will see if I can get out memory stats b4 and after.

ed

[valterb]

Patrick, I don't know if the problem is the same you try to fix (and if I have understood how to check the ram usage: I'm viewing this with "Monitoraggio attività", don't know the name in english but is the graphical way for "top"), but I noticed that opening the same document onwith NeoOffice-2.0_Alpha-Patch-2-Test-2-PowerPC and with OOo2.0.1, both with italian localization, results in a huge difference in ram usage.
For NeoOffice I have 117 MB real memory usage and 874 MB of virtual memory.
For OOo2.0.1 I have 84 MB of real memory and 268 MB of virtual memory.

Is it expected (due to differences of the two software)??

Valter

[OPENSTEP]

The increase in VM usage for Neo is expected due to the Mac VM "pregrabbing" memory for itself even if it is not used. This is the way the Apple VM works and is unavoidable. Unused VM still should not translate to an increase in swap file on hard drive until that memory is actually accessed, so the VM size is really a bogus number.

The "real" memory usage seems fine to me. Other thoughts?

ed

[pluby]

[valterb]

[pluby]

"resident" and "real" are the same thing.

Patrick

[LemonAid]

Patrick,

I downloaded your new patch and tested with "l'ultima avventura del signor bonaventura.odt".
Activity Monitor results: 8168 NeoOffice philip 31.90 15 155.19 MB 1.03 GB
about 155 MB when doing a Print -> Preview. Memory looks reasonable. Just a simple test but seem to show your patch is ... working/doing something good.

Philip ( )

[sardisson]

I did a quick test with a Draw document that I basically could not work on in Neo 1.2 due to perf issues (11x17, ca. 850 objects--imported vector pict of genealogical stuff--but all of 20K in filesize).

I was very impressed with the responsiveness of an un-modded Patch-2: moving all the objects 1px only took about 30 seconds, and when printing, there was enough memory to show the OOo printing dialogue box!

Some quick memory stats:

*un-modded Patch-2 (1.5 GB of RAM in this PB)
After launching Neo 2 (app-only, to a blank Writer doc): 91 MB real mem
After closing Writer doc and opening HW.sxd: 210 MB
After moving 1px and printing to PDF: 226 MB
After closing document and reopening it: 232 MB

* Quit Neo 2, install Test Patch 3:
After launching Neo 2: 134 MB real mem
After opening HW.sxd: 263 MB
After moving 1px and printing to PDF: 276 MB
After closing document and reopening it: 277 MB

"Performance" (responsiveness) was still the same with the test patch as unmodded, but the memory usage seems higher in these rough tests. I don't work on it often, and it's certainly an edge-case on the high end with that many objects, and the rought tests might be poor indicators...so I'm more than happy with being able to edit it usefully in Neo 2 instead of needing Neo/J 1.1

Patrick, if you're interested in testing with this document, I can email it to you privately.

Smokey

[fabriziovenerandi]

I have done some fast basic tests and it seems to works fine, it does not seem to me faster nor slower than the neooffice 1.x release and the memory usage is more or less the same.

unfortunately I can not use neooffice 2 at office (for Oo base problems, not neo's ones) so I use neooffice 2 only on my powerbook. so to have a deep test I have to wait to be alone, no children around, cleaned house, blackberry bush cutted, et ceterae. It's a hard life for betatester too.
If i'll meet with other problems I'll report as soon as I can.


f.

[pluby]