> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of
> Judah Diament
> Sent: Thursday, August 19, 2004 8:45 PM
> To: [EMAIL PROTECTED]
> Subject: how much RAM
>
> how much RAM does a user need to run plucker? any rough
> guesstimates on much bigger compressed files get when
> opened in plucker?
Plucker ran fine on my old Visor Deluxe (8MB) and Visor Pro (16MB), and
currently runs fine on a Tungsten E (32MB). Documents (in excess of a
thousand, occupying about 150MB), reside happily in /Palm/Programs/Plucker
on my 512MB SD card, and formerly resided on a 256MB CF card in a MemPlug
Springboard module on the Pro. (The MemPlug now resides in my SO's Pro.)
Plucker also lives on the card, and is loaded into RAM by the launcher and
executed.
How big files will get when uncompressed depends. Plucker supports "Doc"
format RLE compression, which results in about 40% compression, and also
supports GZip compatible compression if you have sysZlib.prc (shipped with
Plucker) installed. GZipped files get about 70% compression on average.
Which compression method to use in an option in Plucker Desktop/JPluck/PDA
Converter.
As an experiment here, I measured RAM sitting at the launcher screen
(LauncherX 1.11), with Plucker 1.8 loaded from the SD caZrd, looking at the
document list, and with a Plucked version of O'Reilly's Java Reference
Library CD loaded for viewing. The JRL is a 13.5MB Plucker document using
Zlib compression.
Free RAM
--------
Before Plucker: 14,214KB
Plucker loaded: 13,950KB
Plucker viewing JRL: 13,907KB
(Free RAM captured by popping up AKUtils DA over the sessions, and noting
the RAM total given)
Plucker doesn't uncompress the *entire* document to RAM -- just the
requested records -- so it would probably work on a 2MB device, too.
> thanks!
> -Judah
______
Dennis
_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list
