>>>>> Isnur Rochmad writes:
Isnur> At the moment I'm writing a script to poll some nodes with many
Isnur> items to poll, i.e. cpu load, disk load, tcp traffic etc. I
Isnur> take different approach from that of tkined, where I create a
Isnur> job for each node and item. The reason is that I'd like to be
Isnur> able to control the jobs easily. For example, I can stop or
Isnur> modify a particular polling job (to a node) without stopping
Isnur> others. But, I still wonder how much memory would be needed,
Isnur> especially when the number of nodes is large.
Hard to tell without any details. The amount of memory you need
really depends on what you do with the data and how well your code
is written. My experience is that memory is usually not a critical
resource for well written monitoring scripts.
Isnur> One more thing, when I create a job does it mean that I create
Isnur> a new thread ?
No. The job command is just a thin layer on top of the Tcl core event
loop mechanism. It works well if the commands executed by the jobs are
short and non-blocking - such as sending asynchronous polling requests.
Thread support was only recently added to Tcl and the Tnm package has
still many places where it is not thread-safe.
-- Juergen Schoenwaelder Technical University Braunschweig <firstname.lastname@example.org> Dept. Operating Systems & Computer Networks Phone: +49 531 391 3289 Bueltenweg 74/75, 38106 Braunschweig, Germany Fax: +49 531 391 5936 <URL:http://www.ibr.cs.tu-bs.de/~schoenw/>
-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <email@example.com>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.
This archive was generated by hypermail 2b29 : Mon Jan 08 2001 - 15:27:53 MET