You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicecomb.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2018/06/15 03:39:00 UTC
[jira] [Updated] (SCB-240) [pack] performance impacts test
[ https://issues.apache.org/jira/browse/SCB-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang updated SCB-240:
-----------------------------
Description:
as a user, I want to know how much performance loss if I introduce pack as my transaction consistency solution.
We need to deploy the application (which has multiple micro services) and start a client to send the request to the application.
1. Running the application without Omega enabled.
2. Running the application with Omega enabled (without inject the error)
3. Running the application with Omega enabled (with some failed transactions)
In Pack mode, every transaction's call could generate events from Omega to Alpha.
We may need to collect the calling information to optimize to performance.
was:as a user, I want to know how much performance loss if I introduce pack as my transaction consistency solution.
> [pack] performance impacts test
> -------------------------------
>
> Key: SCB-240
> URL: https://issues.apache.org/jira/browse/SCB-240
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Saga
> Affects Versions: saga-0.2.0
> Reporter: Eric Lee
> Priority: Major
> Fix For: saga-0.3.0
>
>
> as a user, I want to know how much performance loss if I introduce pack as my transaction consistency solution.
> We need to deploy the application (which has multiple micro services) and start a client to send the request to the application.
> 1. Running the application without Omega enabled.
> 2. Running the application with Omega enabled (without inject the error)
> 3. Running the application with Omega enabled (with some failed transactions)
>
> In Pack mode, every transaction's call could generate events from Omega to Alpha.
> We may need to collect the calling information to optimize to performance.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)