Re: maximing/resizing multiple x11: change of palette

[Petr M. <mi...@ph...>]

> Somehow I managed to get time to show up...  I can hazard a guess at where
> all the extra CPU time is going, most likely converting ascii characters
> to a double value, based upon the fact that rgb1_from_gray() constitutes
> 100% in the second example and 0% in the first example.  (If I trust the
> numbers I'm seeing, that is... why would cumulative seconds be so small if
> the command takes 80 seconds to run?  Could it be that X is the one really
> using the CPU time? Can't be, otherwise there wouldn't be such a drastic
> time difference between these two scenarios.)

We are back to the complain that the ascii-piped X11 is horribly slow.
Binary transfer (aka OS/2's pm.trm) would boost the performance.


> Petr, are large numbers of (custom) palette colors a concern?  That is,
> anything beyound 2^12 levels?

I never used palette larger than 256. Usually 100. Note that Octave's
default value is 64 -- try:  size(gray)

I don't know whether Octave users treat "truecolor" photographs, where you
need more colors.

--
PM