[RULE] make use of "nice" to prioritize threads, & swap space for preloading?

Michael Fratoni mfratoni at tuxfan.homeip.net
Wed May 21 05:05:38 EEST 2003


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 17 May 2003 08:39 pm, Eugene Wong wrote:
> Hi all.
>
> I tried installing OOo on a 32MB K5 computer, & as you may have
> guessed, it was extremely painful.
>
> I am wondering if there is anything that we can do to preload software
> into the swap partition, when the user isn't using the package. For
> example, I may not intend to use OOo till the end of the day, & I
> wouldn't mind letting the computer devote space cycles to loading it
> into the swap partition. Is it possible? Michael, would you know
> anything about this?

Nope, I don't know anything about it. It doesn't seem likely to help much, 
in any case. There are just some things that require physical memory.

> Also does anybody know how to set the nice level @ the time of
> execution?

"man nice" for details, but basic usage would be:

nice -n program program_args
Where n is a number from -20 (highest priority) to 19 (lowest)

See also "man renice" to alter the priority of a running application.

- -- 
- -Michael

pgp key:  http://www.tuxfan.homeip.net:8080/gpgkey.txt
Red Hat Linux 7.{2,3}|8.0 in 8M of RAM: http://www.rule-project.org/
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+yt7yn/07WoAb/SsRAqL+AJ9LPaeORSWLwscUZolvThevsATOcgCfbGPs
tGqi8s5jJYQ1QJ4E67MmXKo=
=IxLg
-----END PGP SIGNATURE-----



_______________________________________________
Original home page of the RULE project: www.rule-project.org
Original Rule Development Site http://savannah.gnu.org/projects/rule/
Original RULE mailing list: Rule-list at nongnu.org, hosted at http://mail.nongnu.org/mailman/listinfo/rule-list




This full static mirror of the Run Up to Date Linux Everywhere Project mailing list, originally hosted at http://lists.hellug.gr/mailman/listinfo/rule-list, is kept online by Free Software popularizer, researcher and trainer Marco Fioretti. To know how you can support this archive, and Marco's work in general, please click here