I've been doing some load testing with some relatively massive loads (more
than a 1000 clients or so) and I just did a quick stack trace and am seeing a
TON of threads in:
at
org.ops4j.pax.logging.slf4j.Slf4jLoggerFactory.getLogger(Slf4jLoggerFactory.java:92)
at org.slf4j.Logg
est, but that is pretty within the error margin for these
measurements. (The info level log was there so the UUID generator was loaded).
If these scenarios uses UUIDs at all, the type of the generator does not seem
to affect the performance even for this scenario.
> Performance/scalability issue f
amel will auto lookup it
{code:xml}
{code}
> Performance/scalability issue for converter lookup
> --
>
> Key: CAMEL-3123
> URL: https://issues.apache.org/activemq/browse/CAMEL-3123
>
able API for
UUIDs
we can revert back to AMQ based as default, and then just plugin the JDK UUID
based on camel-gae component.
See CAMEL-3139 for some numbers I ran on my local laptop, albeit using a single
thread (easier and quick to setup).
> Performance/scalability issue for converter
that {{activeMQUuidGenerator}}
bean as UUID, when Camel start up.
> Performance/scalability issue for converter lookup
> --
>
> Key: CAMEL-3123
> URL: https://issues.apache.org/activem
e it somehow in the camel context?
> Performance/scalability issue for converter lookup
> --
>
> Key: CAMEL-3123
> URL: https://issues.apache.org/activemq/browse/CAMEL-3123
> Projec
the generator used by Camel.
> Performance/scalability issue for converter lookup
> --
>
> Key: CAMEL-3123
> URL: https://issues.apache.org/activemq/browse/CAMEL-3123
> Project: Apache Camel
http client we are looking to add in the future.
Jetty also has a http client etc.
Anyway glad the numbers is back to normal, or even a bit better.
> Performance/scalability issue for converter lookup
> --
>
>
nges with my scenario: The performance
improved from 210 msg/s with camel 2.4.0 to 3900 msg/s with the version from
the trunk (and 160 concurrent clients), which is even better than the
performance with camel 2.2.0. So I guess that these changes are a very good
thing :-)
> Performance/scal
PropertyEditorTypeConverter as well.
> Performance/scalability issue for converter lookup
> --
>
> Key: CAMEL-3123
> URL: https://issues.apache.org/activemq/browse/CAMEL-3123
> Project: Apache Camel
>
tion committed
> Performance/scalability issue for converter lookup
> --
>
> Key: CAMEL-3123
> URL: https://issues.apache.org/activemq/browse/CAMEL-3123
> Project: Apache Camel
>
en you can maybe try it
out on your system? You need to build from the source yourself.
Yeah anything can break in OSGi. Don't assume it just works, that is the
attitude I use after seining so many issue with it.
> Performance/scalability issue fo
t it might help to keep
all the found editors with the PropertyEditorTypeConverter (is that what you
did?). Might that break some OSGi bundle concept?
> Performance/scalability issue for converter lookup
> --
>
>
http requests to a http proxy.
The total time to do this:
before: 8.5 sec
after: 3.5 sec
By introducing Jetty specific type convertes and letting property editor being
invoked later.
This eliminates the need for property editor being in use in that particular
example.
> Performance/scalability is
the issue.
Its because Jetty has some types for the headers and whatnot which is to be
converted to String.
Providing some Jetty specific type converters and also add a local cache to the
PropertyEditorTypeConverter so the synchronized impact is reduced
> Performance/scalability issue for co
[
https://issues.apache.org/activemq/browse/CAMEL-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-3123:
--
Assignee: Claus Ibsen
> Performance/scalability issue for converter loo
hich causes this on your system?
> Performance/scalability issue for converter lookup
> --
>
> Key: CAMEL-3123
> URL: https://issues.apache.org/activemq/browse/CAMEL-3123
> Project: Apache
[
https://issues.apache.org/activemq/browse/CAMEL-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-3123:
---
Issue Type: Improvement (was: Bug)
> Performance/scalability issue for converter loo
Performance/scalability issue for converter lookup
--
Key: CAMEL-3123
URL: https://issues.apache.org/activemq/browse/CAMEL-3123
Project: Apache Camel
Issue Type: Bug
Components
19 matches
Mail list logo
