[
https://issues.apache.org/jira/browse/QPIDIT-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet closed QPIDIT-15.
----------------------------------
Resolution: Won't Fix
Each test starts its own instance of a JVM, and this takes time. It is a Good
Thing that each test runs in its own environment for reasons of isolation and
the possibility of various environmental differences between tests (this is not
currently the case). However, the price for this approach is that as these
tests run, they take longer owing to the starting and stopping of the JVMs.
The only way to resolve this is to use a single JVM and inject the tests into
that JVM, which adds complexity to the test setup. This is not sufficiently
great a problem to warrant action at this point. There is too much else to do
which is more important right now.
> Tests running on QpidJms shims run slowly compared to ProtonPython shims
> ------------------------------------------------------------------------
>
> Key: QPIDIT-15
> URL: https://issues.apache.org/jira/browse/QPIDIT-15
> Project: Apache QPID IT
> Issue Type: Task
> Components: Qpid Jms Shim
> Reporter: Kim van der Riet
> Assignee: Kim van der Riet
>
> The tests running on QpidJms appear to run slowly (approx 1-2 sec per test)
> compared to the ProtonJms shims which run 5 - 10 tests/second. Find and
> eliminate the cause of the delay; there is no reason why simple operations
> such a sending and receiving < 10 messages of modest size should take so long.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
