You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Chathuri Wimalasena (JIRA)" <ji...@apache.org> on 2012/10/04 22:29:47 UTC
[jira] [Created] (AIRAVATA-594) Improving data retrieval time in
provenance data
Chathuri Wimalasena created AIRAVATA-594:
--------------------------------------------
Summary: Improving data retrieval time in provenance data
Key: AIRAVATA-594
URL: https://issues.apache.org/jira/browse/AIRAVATA-594
Project: Airavata
Issue Type: Bug
Components: Registry API
Affects Versions: 0.4-INCUBATING
Reporter: Chathuri Wimalasena
Fix For: 0.5
When retrieving experiment related data, workflow related data and node information for a specific experiment ID, there are several JPA calls are being called. Replace such methods with pure JDBC queries will improve retrieval time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AIRAVATA-594) Improving data retrieval time in
provenance data
Posted by "Chathuri Wimalasena (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chathuri Wimalasena updated AIRAVATA-594:
-----------------------------------------
Attachment: AIRAVATA-594.patch
Attaching the patch with necessary changes. getExperimentIdByUser(String user), getExperiment(String experimentId) and getExperimentName(String experimentId) methods are being replaced with pure JDBC queries.
> Improving data retrieval time in provenance data
> -------------------------------------------------
>
> Key: AIRAVATA-594
> URL: https://issues.apache.org/jira/browse/AIRAVATA-594
> Project: Airavata
> Issue Type: Bug
> Components: Registry API
> Affects Versions: 0.4-INCUBATING
> Reporter: Chathuri Wimalasena
> Fix For: 0.5
>
> Attachments: AIRAVATA-594.patch
>
>
> When retrieving experiment related data, workflow related data and node information for a specific experiment ID, there are several JPA calls are being called. Replace such methods with pure JDBC queries will improve retrieval time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AIRAVATA-594) Improving data retrieval time in
provenance data
Posted by "Lahiru Gunathilake (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lahiru Gunathilake resolved AIRAVATA-594.
-----------------------------------------
Resolution: Fixed
We might have to do more but for the time being resolving this issue since we have achieved reasonable amount of performance.
Lahiru
> Improving data retrieval time in provenance data
> -------------------------------------------------
>
> Key: AIRAVATA-594
> URL: https://issues.apache.org/jira/browse/AIRAVATA-594
> Project: Airavata
> Issue Type: Bug
> Components: Registry API
> Affects Versions: 0.4-INCUBATING
> Reporter: Chathuri Wimalasena
> Fix For: 0.5
>
> Attachments: AIRAVATA-594.2.patch, AIRAVATA-594.patch
>
>
> When retrieving experiment related data, workflow related data and node information for a specific experiment ID, there are several JPA calls are being called. Replace such methods with pure JDBC queries will improve retrieval time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (AIRAVATA-594) Improving data retrieval time in
provenance data
Posted by "Lahiru Gunathilake (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lahiru Gunathilake closed AIRAVATA-594.
---------------------------------------
> Improving data retrieval time in provenance data
> -------------------------------------------------
>
> Key: AIRAVATA-594
> URL: https://issues.apache.org/jira/browse/AIRAVATA-594
> Project: Airavata
> Issue Type: Bug
> Components: Registry API
> Affects Versions: 0.4-INCUBATING
> Reporter: Chathuri Wimalasena
> Fix For: 0.5
>
> Attachments: AIRAVATA-594.2.patch, AIRAVATA-594.patch
>
>
> When retrieving experiment related data, workflow related data and node information for a specific experiment ID, there are several JPA calls are being called. Replace such methods with pure JDBC queries will improve retrieval time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AIRAVATA-594) Improving data retrieval time in
provenance data
Posted by "Chathuri Wimalasena (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chathuri Wimalasena updated AIRAVATA-594:
-----------------------------------------
Attachment: AIRAVATA-594.2.patch
I was missing a space in the sql query in the previous patch. Attaching the updated patch. Sorry for the inconvenience.
> Improving data retrieval time in provenance data
> -------------------------------------------------
>
> Key: AIRAVATA-594
> URL: https://issues.apache.org/jira/browse/AIRAVATA-594
> Project: Airavata
> Issue Type: Bug
> Components: Registry API
> Affects Versions: 0.4-INCUBATING
> Reporter: Chathuri Wimalasena
> Fix For: 0.5
>
> Attachments: AIRAVATA-594.2.patch, AIRAVATA-594.patch
>
>
> When retrieving experiment related data, workflow related data and node information for a specific experiment ID, there are several JPA calls are being called. Replace such methods with pure JDBC queries will improve retrieval time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira