Hello Ant,
Thanks for the reply, sounds intersting. We are just in the phase of
prototype implementations. So if you can commit the sample it would be great
to get some grip on.
Thanks,
Holger
On 10/26/07, ant elder [EMAIL PROTECTED] wrote:
On 10/26/07, Holger Winkelmann [EMAIL PROTECTED]
Can't comment to the exact overhead, but we are getting really good performance
metrics from Apache Tuscany on websphere 6.1, something within the range of
three to four hundred transactions per second with the CPU at around 60%. And
message sizes of about a kilobyte.
Charles can you elaborate
Do you mean the E4X sample, if so sure but it will take a little while to
get it going again with the latest code. So does that mean JavaScript and
E4X are languages you are interested in using? And how about others like
Ruby or Groovy or what else would you use?
...ant
On 10/26/07, Holger
When running a striped down version of our application (no complex business
logic, only simple Rq/Rs [1k each]) we see TPS rates around 400+ with about 60%
CPU utilization. Response times are below 100ms.
Sorry Holger but we didn't push our app to the CPU limit, but I'm sure we could
get up
I just think below 3 bindings are more important than others:
1. binding.ws OK
2. binding.ejb --- reference or say, import, OK; service or say,
export, not ready.
3. binding.jms --- Not ready.
They should be in release ASAP. I will try source code. Thanks!
On 10/23/07,
