> Yes, you are right. My measurements doesn't account > for the background thread processing time since it use > the pattern observer/observable(more like publish and > subscribe but in-process).
Performance has many dimensions. You're talking about absolute intervals for a single operation. If you care about scalability, you definitely want to account for the resources used by the background threads. At some point, the machine has to do the work, one way or another. Also, you cited measurements that included start-up costs. Unless you have a fairly trivial application which doesn't live long, you might want to consider factoring out the start-up costs as not mattering much in the steady state. (If you do have such an application, you're probably being killed by JVM start-up overhead in the first place.) Anyhow, maybe you already know all this and you're measuring things just the way you want to measure them. For a pretty significant percentage of developers and applications, the above two points are pretty pertinent, though. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
