Hi all, Wow.. Interesting... I did some tests some time back with the objective of testing the effectiveness of Axis2 attachment file caching.. IIRC I was able to upload a 800 MB file in about 35 mins time using the same machine as server and the client.. Cannot remember the machine configuration I used.
IMHO the tests needs be done in both ways with/without file caching. In the latter case we'll not be able to test with large attachments.
* Client sends "Hello" --> Server returns attachment
+1.. I would like to add the reverse of this too... Client uploads a file..
* Attachment echo
+1
* On-the-fly generation (instead of file reading)
We need to make sure that we write out whatever we generate as an when they are generated, If not we might run in to out of memory situations with larger sizes.
* On-the-fly process (instead of file writing) * Stress testing (multiple concurrent clients)
+1 Keep us informed. More than willing to hear the results.. :) ~Thilina On 12/13/06, Rodrigo Ruiz <[EMAIL PROTECTED]> wrote:
Hi Philipp, I am afraid I have no results to contribute at this moment, but I will :-) By TCP/IP stack and File I/O implementations I was referring to the internal implementation of these subsystems in each OS. Typically, Linux and Solaris have more robust and performant implementations of TCP/IP than Windows 2000 Pro or XP, as the latter are more workstation-oriented while the former are more server-oriented. With a few rare exceptions, specifying the OS you are giving enough information about the TCP/IP implementation. The File I/O subsystem is different. The performance profile will depend on the filesystem and the Operating System. In Windows you may find FAT32 and NTFS filesystems, in Linux you can have a lot of possibilities, and other OSs have their own propietary filesystems. All of them have different performance/robustness characteristics. Axis2 has a wiki, and I suppose we could use it, at least for setting up a starting point and/or for the first results. Of course, if more people join us, and we collect lots of results, a wiki will not be the correct tool. You can find a link to the wiki in the Axis2 home page left menu. Back to the benchmark, I think there are a few more scenarios to take into account (this is, for a general benchmark): * Test the impact of other specifications: * WS-SecureConversation * WS-ReliableMessage * Client sends "Hello" --> Server returns attachment * Attachment echo * On-the-fly generation (instead of file reading) * On-the-fly process (instead of file writing) * Stress testing (multiple concurrent clients) Does any of these scenarios make sense to you? Cheers, Rodrigo -- ------------------------------------------------------------------- GRID SYSTEMS, S.A. Rodrigo Ruiz Parc Bit - Edificio 17 Research Coordinator 07121 Palma de Mallorca [EMAIL PROTECTED] Baleares - Spain Tel: +34 971 435 085 http://www.gridsystems.com/ Fax: +34 971 435 082 ------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Thilina Gunarathne WSO2, Inc.; http://www.wso2.com/ Home page: http://webservices.apache.org/~thilina/ Blog: http://thilinag.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
