New subject: Not writing silly slow programs.

[Paul E Johnson]

"Marcus G. Daniels" wrote:
> 
> 
> Profiling the program is a good place to start.
> 
> $ jdkswarm -prof FooBar
> 
> ..then look at java.prof.
> 
> One possible expense is lots of back-and-forth between Objective C and Java...
> 
OK, since I've never written a Java Swarm, but plan to, I want to know
more about what you mean by this, because I'm afraid of writing slow
programs.  What do you mean by "back-and-forth"?  I'm guessing, for
example, that in an agent that is a Java object, I'd better not be
making any unnecessary usage of Swarm objects. I.e, use Java
collections, and whatever else Java, rather than subclassing Swarm Lists
and such. 

Right? What else is important?

Ideally, Swarm is supplying the scheduling, but nothing else?

Just a brief list will satisfy me here, I don't have background to
understand a tun of stuff.  But I want to know what to avoid.

-- 
Paul E. Johnson                       email: address@hidden
Dept. of Political Science            http://lark.cc.ukans.edu/~pauljohn
University of Kansas                  Office: (785) 864-9086
Lawrence, Kansas 66045                FAX: (785) 864-5700

                  ==================================
   Swarm-Support is for discussion of the technical details of the day
   to day usage of Swarm.  For list administration needs (esp.
   [un]subscribing), please send a message to <address@hidden>
   with "help" in the body of the message.