Hi Philipp,

I think some benchmarks on data transfers would be very useful to all of us. Maybe we could put the results into the wiki, so everybody can read them, and contribute. Or being more ambitious, somebody could even consider to start an independent project, in order to compare different SOAP stack implementations.

I have some comments about the data you provide  :-)

* I think the benchmark is basically OK. I suppose you are measuring total round-trip times, aren't you? * You don't mention anything about mean times. Although a single execution may be enough for large attachments, for small ones it would be useful to repeat the invocation several times, and obtain means and deviations. * Personally, my opinion is that having both, client and server, on the same host is not the most typical scenario, but I think it still must be included in any benchmark, as it has its own particularities. I will come back to this later. * In order to ensure that the results can be compared, sooner or later a common source code should be used. This one smells to a project ;-)

* You have not included information about your disk in your configuration. As you are writing the attachment to disk, its characteristics are relevant (IDE / SATA, rpm, and the like). Depending on the OS, the filesystem should be also specified. * The Operating System is also missing. TCP/IP stack implementations are totally different between OSs, and the same can be said about disk I/O. It also influence the default JVM settings. * The JVM version is another important field to include in the configuration. And also its configuration flags (GC policies, etc.)
* Just for curiosity, do you really have 1028MB, or is it an errata? :-D

* The file sizes look a bit arbitrary. Maybe it would be better to use "nicer" sizes ;-) * The times you have obtained show a rather poor performance. I am just guessing now but, does your client get the attachment data from a file? Reading and writing on the same disk may be the cause for these long times. If this is the case, you could try to generate the data on the fly and see how the figures change. You are using rather small sizes, so you could use in-memory byte arrays with random data.


Hey, this seems to me a very good subject to work on, specially now that SPEC has cancelled its web service benchmark project (AppPlatform).


Best regards,
Rodrigo Ruiz

Philipp Perner wrote:
Hi,

Does anyone have benchmarks of the current releases, when trying to use SwA with MTOM?
Many people wrote, that they transfer files with up to 100MB.
But what are the performances of these web-services? And what configuration, web-server and hardware do they use?

To start this topic, I would like to post some figures I came up using my webService: My Web-Service receives a datahandler which is written to harddisc. After successfull writing it sends a string "success" back to the client.
Both, client and server, are localhost.

Web-Server: Apache Tomcat 5.0.28
Version of Axis: Apache Axis2 1.1
Used Modules: Apache Rampart 1.1
Databinding: ADB
Attachment Type: Base64Binary
Hardware: Intel P4 3.2 GHz with 1028MB Ram
Java Key Stores: service.jks and client.jks from rampart samples

Here are the benchmarks:
no rampart items:
size 10 kb: 188ms
size 2753kb: 15.183 sec
size 14214 kb: 81.001 sec

rampart items: timestamp signature
size 10 kb: 242ms
size 2753kb: 13.594 sec
size 14214 kb: 108.829 sec

rampart items: timestamp signature encrypt
size 10 kb: 297 ms
size 2753kb: 19,484 sec
size 14214 kb: 173,579 sec

I would appreciate if someone could send some benchmarks, or at least comment on my figures. Are these usual transaction times? Which times occur when sending files up to 100MB?

cheers,

Philipp


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to