Hi all,
I knocked up a quick GOP load-averages display "load.pd", it's a bit minimal but it does what I want it to do. It displays load averages for 1/4, 1/2, 1, 2, 4 seconds, which is handy if your patch is "bursty"[1] in CPU usage which makes having a one second granularity a bit useless. The short patch name is so that it fits inside the GOP box (hopefully).
Claude
[1] For example, Gridflow currently does all its processing in message-time, which means that one message often triggers lots of calculation in a burst.
There seems to be two files to this load.pd and load_average.pd The
attached inline Pd file seems to be one files. Could you disambiguate?
.hc
On Jan 14, 2006, at 4:14 AM, Claude Heiland-Allen wrote:
Hi all,
I knocked up a quick GOP load-averages display "load.pd", it's a bit
minimal but it does what I want it to do. It displays load averages
for 1/4, 1/2, 1, 2, 4 seconds, which is handy if your patch is
"bursty"[1] in CPU usage which makes having a one second granularity a
bit useless. The short patch name is so that it fits inside the GOP
box (hopefully).Claude
[1] For example, Gridflow currently does all its processing in
message-time, which means that one message often triggers lots of
calculation in a burst.--
http://claudiusmaximus.goto10.org #N canvas 10 10 300 127 10; #X obj 11 12 load; #X text 70 12 Load averages!; #X text 70 44 Graph on parent!; #X text 71 73 Minimal look!; #X coords 0 0 1 1 44 100 0; #N canvas 25 95 300 127 10; #X floatatom 11 26 5 0 0 0 - - -; #X floatatom 11 42 5 0 0 0 - - -; #X floatatom 11 58 5 0 0 0 - - -; #X floatatom 11 74 5 0 0 0 - - -; #X floatatom 11 90 5 0 0 0 - - -; #X obj 75 46 load_average 1000; #X obj 42 8 tgl 10 0 empty empty empty 0 -6 0 8 -262144 -1 -1 1 1; #X obj 201 4 loadbang; #X msg 201 25 1; #X obj 75 6 load_average 250; #X obj 75 26 load_average 500; #X obj 75 66 load_average 2000; #X obj 75 86 load_average 4000; #X connect 5 0 2 0; #X connect 6 0 5 0; #X connect 6 0 9 0; #X connect 6 0 10 0; #X connect 6 0 11 0; #X connect 6 0 12 0; #X connect 7 0 8 0; #X connect 8 0 6 0; #X connect 9 0 0 0; #X connect 10 0 1 0; #X connect 11 0 3 0; #X connect 12 0 4 0; #X coords 0 -1 1 1 44 100 1 8 8; #N canvas 10 10 300 201 10; #X obj 31 31 inlet start; #X obj 31 121 cputime; #X obj 31 101 t b b; #X obj 123 31 inlet period; #X obj 31 81 metro 1000; #X obj 31 141 / 1000; #X obj 31 171 outlet load; #X obj 218 31 loadbang; #X obj 218 51 float $1; #X obj 123 51 moses 1; #X obj 169 97 loadbang; #X msg 169 117 1; #X connect 0 0 4 0; #X connect 1 0 5 0; #X connect 2 0 1 0; #X connect 2 1 1 1; #X connect 3 0 9 0; #X connect 4 0 2 0; #X connect 5 0 6 0; #X connect 7 0 8 0; #X connect 8 0 9 0; #X connect 9 1 4 1; #X connect 9 1 5 1; #X connect 10 0 11 0; #X connect 11 0 4 0; _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
"Terrorism is not an enemy. It cannot be defeated. It's a tactic.
It's about as sensible to say we declare war on night attacks and
expect we're going to win that war. We're not going to win the war on
terrorism."
- retired U.S. Army general,
William Odom
Hans-Christoph Steiner wrote:
There seems to be two files to this load.pd and load_average.pd The
attached inline Pd file seems to be one files. Could you disambiguate?
Ok.
.hc
On Jan 14, 2006, at 4:14 AM, Claude Heiland-Allen wrote:
Hi all,
I knocked up a quick GOP load-averages display "load.pd", it's a bit
minimal but it does what I want it to do. It displays load averages
for 1/4, 1/2, 1, 2, 4 seconds, which is handy if your patch is
"bursty"[1] in CPU usage which makes having a one second granularity a bit useless. The short patch name is so that it fits inside the GOP box (hopefully).Claude
[1] For example, Gridflow currently does all its processing in
message-time, which means that one message often triggers lots of
calculation in a burst.
This is attachment load-help.pd
#N canvas 10 10 300 127 10; #X obj 11 12 load; #X text 70 12 Load averages!; #X text 70 44 Graph on parent!; #X text 71 73 Minimal look!; #X coords 0 0 1 1 44 100 0;
This is attachment load.pd
#N canvas 25 95 300 127 10; #X floatatom 11 26 5 0 0 0 - - -; #X floatatom 11 42 5 0 0 0 - - -; #X floatatom 11 58 5 0 0 0 - - -; #X floatatom 11 74 5 0 0 0 - - -; #X floatatom 11 90 5 0 0 0 - - -; #X obj 75 46 load_average 1000; #X obj 42 8 tgl 10 0 empty empty empty 0 -6 0 8 -262144 -1 -1 1 1; #X obj 201 4 loadbang; #X msg 201 25 1; #X obj 75 6 load_average 250; #X obj 75 26 load_average 500; #X obj 75 66 load_average 2000; #X obj 75 86 load_average 4000;
This is attachment load-average.pd
#X connect 5 0 2 0; #X connect 6 0 5 0; #X connect 6 0 9 0; #X connect 6 0 10 0; #X connect 6 0 11 0; #X connect 6 0 12 0; #X connect 7 0 8 0; #X connect 8 0 6 0; #X connect 9 0 0 0; #X connect 10 0 1 0; #X connect 11 0 3 0; #X connect 12 0 4 0; #X coords 0 -1 1 1 44 100 1 8 8; #N canvas 10 10 300 201 10; #X obj 31 31 inlet start; #X obj 31 121 cputime; #X obj 31 101 t b b; #X obj 123 31 inlet period; #X obj 31 81 metro 1000; #X obj 31 141 / 1000; #X obj 31 171 outlet load; #X obj 218 31 loadbang; #X obj 218 51 float $1; #X obj 123 51 moses 1; #X obj 169 97 loadbang; #X msg 169 117 1; #X connect 0 0 4 0; #X connect 1 0 5 0; #X connect 2 0 1 0; #X connect 2 1 1 1; #X connect 3 0 9 0; #X connect 4 0 2 0; #X connect 5 0 6 0; #X connect 7 0 8 0; #X connect 8 0 9 0; #X connect 9 1 4 1; #X connect 9 1 5 1; #X connect 10 0 11 0; #X connect 11 0 4 0;
This is displayed as attachment "Part 1.5" in my mail client
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
I must say that my mail client showed them as 4 attachments, and that looking at the message source showed that it was indeed a MIME-multipart message.
Oops, I made an error...
Claude Heiland-Allen wrote:
Hans-Christoph Steiner wrote:
There seems to be two files to this load.pd and load_average.pd The
attached inline Pd file seems to be one files. Could you disambiguate?Ok.
.hc
On Jan 14, 2006, at 4:14 AM, Claude Heiland-Allen wrote:
Hi all,
I knocked up a quick GOP load-averages display "load.pd", it's a bit
minimal but it does what I want it to do. It displays load averages
for 1/4, 1/2, 1, 2, 4 seconds, which is handy if your patch is
"bursty"[1] in CPU usage which makes having a one second granularity a bit useless. The short patch name is so that it fits inside the GOP box (hopefully).Claude
[1] For example, Gridflow currently does all its processing in
message-time, which means that one message often triggers lots of
calculation in a burst.This is attachment load-help.pd
#N canvas 10 10 300 127 10; #X obj 11 12 load; #X text 70 12 Load averages!; #X text 70 44 Graph on parent!; #X text 71 73 Minimal look!; #X coords 0 0 1 1 44 100 0;
This is attachment load.pd
#N canvas 25 95 300 127 10; #X floatatom 11 26 5 0 0 0 - - -; #X floatatom 11 42 5 0 0 0 - - -; #X floatatom 11 58 5 0 0 0 - - -; #X floatatom 11 74 5 0 0 0 - - -; #X floatatom 11 90 5 0 0 0 - - -; #X obj 75 46 load_average 1000; #X obj 42 8 tgl 10 0 empty empty empty 0 -6 0 8 -262144 -1 -1 1 1; #X obj 201 4 loadbang; #X msg 201 25 1; #X obj 75 6 load_average 250; #X obj 75 26 load_average 500; #X obj 75 66 load_average 2000; #X obj 75 86 load_average 4000;
This is attachment load-average.pd
Actually, it's the last half of load.pd
#X connect 5 0 2 0; #X connect 6 0 5 0; #X connect 6 0 9 0; #X connect 6 0 10 0; #X connect 6 0 11 0; #X connect 6 0 12 0; #X connect 7 0 8 0; #X connect 8 0 6 0; #X connect 9 0 0 0; #X connect 10 0 1 0; #X connect 11 0 3 0; #X connect 12 0 4 0; #X coords 0 -1 1 1 44 100 1 8 8;
This really is load_average.pd
#N canvas 10 10 300 201 10; #X obj 31 31 inlet start; #X obj 31 121 cputime; #X obj 31 101 t b b; #X obj 123 31 inlet period; #X obj 31 81 metro 1000; #X obj 31 141 / 1000; #X obj 31 171 outlet load; #X obj 218 31 loadbang; #X obj 218 51 float $1; #X obj 123 51 moses 1; #X obj 169 97 loadbang; #X msg 169 117 1; #X connect 0 0 4 0; #X connect 1 0 5 0; #X connect 2 0 1 0; #X connect 2 1 1 1; #X connect 3 0 9 0; #X connect 4 0 2 0; #X connect 5 0 6 0; #X connect 7 0 8 0; #X connect 8 0 9 0; #X connect 9 1 4 1; #X connect 9 1 5 1; #X connect 10 0 11 0; #X connect 11 0 4 0;
This is displayed as attachment "Part 1.5" in my mail client
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-listI must say that my mail client showed them as 4 attachments, and that looking at the message source showed that it was indeed a MIME-multipart message.
Claude