Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


verify. | 16 comments | Create New Account
Click here to return to the 'verify.' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
verify.
Authored by: charlietuna on Oct 09, '01 09:06:54AM

For those of us who are skeptical, how would we know that our windows are getting compressed? How does Mr. Welch know that his windows are getting such-and-such compression?



[ Reply to This | # ]
verify.
Authored by: Anonymous on Oct 09, '01 11:25:59AM

the compression:
start your console and monitor console.log.
from time to time you'll see a line stating that a "compressed window was flushed" by the windowserver.

the ratio:
well, i guess it's in the numbers he provided. look at the line that contains "ratio".

not too sure about both, though... :)

i noticed that app-switching is A LOT faster than before. may be imagination, but who cares? ;) if it *feels* faster, it's ok with me.



[ Reply to This | # ]
It works for me!!!
Authored by: sungwoo on Oct 09, '01 02:09:34PM

I tested with eight applications which mixed as a carbon, cocoa, and classic applications.
On my Wallstreet 233MHz, it works as Mr. Welch claimed. Way faster than before!!
I can say that the switching app shows me an instant redraw. hmm...
However, I am not sure this really reduce the RAM usage. Maybe I tested with too small number of applications?

Also, I have a same question.
Why the ratio (8.5:1) is specifically suggested?
And if I wanna change it as 10:1, what value should I use? (any example plz?)

Sungwoo



[ Reply to This | # ]
verify.
Authored by: werikblack on Oct 24, '02 12:59:50PM
The information given is accurate. If you look at top, a lot of times the processor's doing almost nothing, and the bus going to the processor is saturated. Just doing the math, the processor is running at 2x1.25 GHz on the high-end machines, but data is only getting there at 167 MHz. Granted, this is oversimplified and doesn't take into account a number of other factors, but that's a pretty big disparity. To verify window buffer compression, you have to have the developer tools installed.
  • Launch /Developer/Applications/Quartz Debug.
  • Click "Show Window List."
  • View values in the kBytes column. These tell how many K RAM your windows are using
If the value has a "C" appended to the end of it, this means the window buffer is compressed.

[ Reply to This | # ]