-
Bug
-
Resolution: Obsolete
-
Major
-
EAP 5.0.0.CR5
-
None
-
Not Required
We need to look for ws server side optimizations to address the slight perfomance loss of EAP v5 vs EAP 4.3 due to more features implemented and supported.
The attached simple bench test can be used as a starting point and gives the following results:
- EAP 4.3 CP06: 599.3 msgs/s
- EAP 5.0 CR5: 445.18 msgs/s
- is blocked by
-
JBPAPP-3183 JBossWS - JBossWSEntityResolver should cache properties
- Resolved
-
JBPAPP-3241 JBossWS - Ineffective implementation of string normalize method
- Resolved
-
JBPAPP-3251 JBossWS - Optimize DefaultEndpoint.getTargetBeanClass() method
- Resolved
-
JBPAPP-3261 JBossWS - Remove useless DOMUtils.parse() method calls during deserialization process
- Resolved
-
JBPAPP-3177 JBossWS - Cache resource name lookup through Services API
- Closed
-
JBWS-2436 Look for eventual optimizations when scanning classes
- Closed
- is related to
-
JBPAPP-3303 JBossWS - Increase DOMUtils performances optimizing DocumentBuilder creation
- Resolved