Hmmm, Interesting. There seem to be a problem in C client in case of
large attachments.
This must be due to the fact that we are using a loop to read the file.
If we stat and read the file at once, there could be an improvement.
Why is it so slow, in C vs C case? (Third column) This is worth
investigating.
Thanks,
Samisa...
Kapila Dissanayake wrote:
Hi,
I did some testing on binary attachment transfer times, with axis2
'java' and 'C' servers with sample mtom clients. It took very high
transfer times for large size attachments. Some minor modificaions
were done to the data_handler.c and it was sent to the mailing list.
(File Size) vs (Time Taken in milli seconds) to transfer binary
attachments
Environment
----------
Processor - Intel Celeron M 1.40GHz
RAM - 256 MB
OS - Fedora Core 4.
Java Server - axis2 Java
C Server - axis2
mtom C and java test clients were used
Time Taken in milli seconds
File Size (kb)
Java Server
(ms)
Java Server
(ms)
C Server
(ms)
C Server
(ms)
Java Client
(ms)
C Client
(ms)
C Client
(ms)
Java Client
(ms)
---------------
---------------
---------------
---------------
---------------
---------------
---------------
---------------
---------------
28
445
274
2004
1009
38
617
297
1957
842
132
593
527
2181
726
154
551
447
2081
677
165
440
743
2147
676
561
1029
418
2581
1075
762
2137
1572
3231
2356
1162
3172
2962
3981
3100
1761
7672
5494
8186
3041
2081
7768
6837
11757
3499
4241
14465
24060
36168
Could not transfer (Error Occured in Java client)
Thank You
Kapila
