[JBoss JIRA] (TEIID-3404) Teiid DatabaseAppender JPA perisist Command log consume high CPU
by Kylin Soong (JIRA)
[ https://issues.jboss.org/browse/TEIID-3404?page=com.atlassian.jira.plugin... ]
Kylin Soong updated TEIID-3404:
-------------------------------
Description:
I have 4 - 5 concurrent client query to Portfolio VDB, this cause log DatabaseAppender JPA perisist Command log thread consume high CPU. In my test, one log threads always swallow high CPU, if the concurrent client query more than 10, it swallow 100% cpu.
[1] have detailed reproduce steps, including thread dumps.
[1] https://github.com/kylinsoong/teiid-samples/tree/master/command-logging-h...
was:
I have 4 - 5 concurrent client query to Portfolio VDB, these cause log DatabaseAppender JPA perisist Command log thread consume high CPU. In my test, one log threads always swallow high CPU, if the concurrent client query more than 10, it swallow 100% cpu.
[command-logging-highcpu](https://github.com/kylinsoong/teiid-samples/tree... have detailed reproduce steps.
Environment:
* DV 6.1
* dynamicvdb-datafederation quickstart
was:
* DV 6.1
* [dynamicvdb-datafederation](https://github.com/teiid/teiid-quickstarts/tre...
> Teiid DatabaseAppender JPA perisist Command log consume high CPU
> ----------------------------------------------------------------
>
> Key: TEIID-3404
> URL: https://issues.jboss.org/browse/TEIID-3404
> Project: Teiid
> Issue Type: Bug
> Components: Tools
> Affects Versions: 8.7.1
> Environment: * DV 6.1
> * dynamicvdb-datafederation quickstart
> Reporter: Kylin Soong
> Assignee: Steven Hawkins
>
> I have 4 - 5 concurrent client query to Portfolio VDB, this cause log DatabaseAppender JPA perisist Command log thread consume high CPU. In my test, one log threads always swallow high CPU, if the concurrent client query more than 10, it swallow 100% cpu.
> [1] have detailed reproduce steps, including thread dumps.
> [1] https://github.com/kylinsoong/teiid-samples/tree/master/command-logging-h...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (TEIID-3403) jaxrs version conflict in teiid jboss integration
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3403?page=com.atlassian.jira.plugin... ]
Ramesh Reddy resolved TEIID-3403.
---------------------------------
Labels: Alpha1 (was: )
Resolution: Done
Created a new module called "teiid-jboss-security" and moved the CXF specific code in there. Moved the dependencies and reconfigured rest-service to org.jboss.teiid module
> jaxrs version conflict in teiid jboss integration
> -------------------------------------------------
>
> Key: TEIID-3403
> URL: https://issues.jboss.org/browse/TEIID-3403
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.11
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Blocker
> Labels: Alpha1
> Fix For: 8.11
>
>
> There is a version conflict with the cxf and resteasy jaxrs dependency in jboss integration.
> The cxf dependency may need to be separated to a different module.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months
[JBoss JIRA] (TEIID-3390) Improve SQL/XML generation performance and limit disk usage
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3390?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3390:
---------------------------------------
Based upon TeiidRSProviderPost in Designer this will be a problem for them. I can add a connection option do allow implicit cleanup for embedded connections as a workaround - if we want older designer wars to still work. Ideally they will need to update their code.
> Improve SQL/XML generation performance and limit disk usage
> -----------------------------------------------------------
>
> Key: TEIID-3390
> URL: https://issues.jboss.org/browse/TEIID-3390
> Project: Teiid
> Issue Type: Enhancement
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.11
>
>
> Deeply nested large xml documents generated by SQL/XML can create a lot of temporary disk backed objects. These objects can have slow cleanup based upon when their references get cleared.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
9 years, 10 months