How can I speed up cnet?
• Don’t print out gallons of debug information to each node’s output window. The printing of large anounts of text and scrolling these windows obviously slows down cnet. Print out bad news, not good news. • If you think your protocol works “for a few minutes” but then dies a death, change a few attributes to speed up the cnet world. For example: messagerate = 3ms propagationdelay = 1ms should make your protocol “work for a few seconds” Much better. • If you’d rather not wait a full second for cnet to complete one second of network activity, run with the -T option to force events to be scheduled immediately (nodeinfo.time_in_ms is updated as you’d hope). • You don’t need an X-terminal to run cnet; it’ll run from either a PC or an ASCII terminal and detect that it is not running under X. Then you can use the -o option or explicitly send output to stdout, stderr or a file rather than expecting it to appear in its own stdout window. After a while the gimmick of the “network map” shou
