I've tryied to use -Xrunhprof with various options but I haven't
obtaines any useful info because I have no clues about the use of the
java profiler. In any case, I've continued testing different situations
with both jvm and most of the cases with similar marks.
Only one case performs dramatically slow in sun 1.4, whe component tag
is used in a jsp.
I've tested many webwork examples with similar results in any jvm, but
the formtest example, that uses component tag in formtest.jsp really
demonstrates there is a problem somewhere, not necessarily in webwork:
With the use of HitUrl example (very useful btw) this is the score after
a warm-up of some hits:
Count:10
Thread Count:4
sun sdk 1.4 (best of 3 times):
Total time: 437,281 (7 min:17 sec)
Average time: 43,728 (0 min:43 sec)
Mean time: 48,771 (0 min:48 sec)
Fastest time: 24,364 (0 min:24 sec)
Slowest time: 49,402 (0 min:49 sec)
IBM jdk 1.3 (best of 3 times):
Total time: 13,314 (0 min:13 sec)
Average time: 1,331 (0 min:1 sec)
Mean time: 1,362 (0 min:1 sec)
Fastest time: 837 (0 min:0 sec)
Slowest time: 1,886 (0 min:1 sec)
the numbers are really explicit, we (or sun) have a problem.
Xavi
El mar, 02-04-2002 a las 14:35, Rickard escribió:
>
> It would be good if you could do a profile of where the time is actually
> spent. I.e. is this really a WebWork problem?
>
> /Rickard
>
> --
> Rickard Öberg
>
>
>
> _______________________________________________
> Webwork-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/webwork-user
_______________________________________________
Webwork-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webwork-user
