Mailinglist Archive: opensuse (4054 mails)
| < Previous | Next > |
RE: [SLE] OO: If you can make it, I can break it!
- From: "Carlos E. R." <robin1.listas@xxxxxxxxxx>
- Date: Sun, 1 Jan 2006 13:16:37 +0100 (CET)
- Message-id: <Pine.LNX.4.61.0601011308590.28060@xxxxxxxxxxxxxxxx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Saturday 2005-12-31 at 22:49 -0900, Greg Wallace wrote:
> If it sounded like I was ranting I certainly didn't intend that. I think
> OO works fine, at least on my machine. When I entered this thread, there
> seemed to be a question of whether the caching done by OO was a drag on the
> system and there was talk of it needing to be turned off,
I think your confusion is that you think this cacheing is done by OOo. It
is not, it is done by the kernel, the same as it is done for every single
application and file read or written in the system. OOo knows nothing
about it, it is transparent.
The only thing that OOo can do, with the quickstarter, is to run another
app whose task is simply to say to the system: "I want to use such and
such libraries, so please activate, load, run them or whatever you have to
do so I can use them" - except that it really doesn't use them, but the
result is that they are loaded ready for when the user really decides to
run OOo.
It is just a trick.
This doesn't have anything to do with cache, it occupies memory with
binaries, leaving less memory for other uses - like cache, for instance:
it will in fact slow down other system uses.
- --
Cheers,
Carlos Robinson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFDt8gntTMYHG2NR9URAm7EAJ91zyM+Xpmbr0lQQnE+9rEe0Y2wAACgmVuU
a9Vv6/gnT+42KuI3Lls8Bns=
=qQZo
-----END PGP SIGNATURE-----
Hash: SHA1
The Saturday 2005-12-31 at 22:49 -0900, Greg Wallace wrote:
> If it sounded like I was ranting I certainly didn't intend that. I think
> OO works fine, at least on my machine. When I entered this thread, there
> seemed to be a question of whether the caching done by OO was a drag on the
> system and there was talk of it needing to be turned off,
I think your confusion is that you think this cacheing is done by OOo. It
is not, it is done by the kernel, the same as it is done for every single
application and file read or written in the system. OOo knows nothing
about it, it is transparent.
The only thing that OOo can do, with the quickstarter, is to run another
app whose task is simply to say to the system: "I want to use such and
such libraries, so please activate, load, run them or whatever you have to
do so I can use them" - except that it really doesn't use them, but the
result is that they are loaded ready for when the user really decides to
run OOo.
It is just a trick.
This doesn't have anything to do with cache, it occupies memory with
binaries, leaving less memory for other uses - like cache, for instance:
it will in fact slow down other system uses.
- --
Cheers,
Carlos Robinson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFDt8gntTMYHG2NR9URAm7EAJ91zyM+Xpmbr0lQQnE+9rEe0Y2wAACgmVuU
a9Vv6/gnT+42KuI3Lls8Bns=
=qQZo
-----END PGP SIGNATURE-----
| < Previous | Next > |