[
https://issues.apache.org/jira/browse/TAJO-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14371536#comment-14371536
]
Dongjoon Hyun commented on TAJO-1430:
-------------------------------------
Hi, [~hyunsik].
According to your kind guide, I created another PreparedStatement issue. I will
improve Tajo PreparedStatement officially. But, please note its limitation
also. TajoCli and normal Statement will not be improved there.
For this issue, I will add the cache size limitation too. We can clear the
cache regularly or handle in a LRU pattern. Please see the positive effect for
Tajo. In fact, I'm working on `Hi-speed Tajo` project. We want to make Tajo 5
times faster.
If you allow me, I will create an Umbrella issue for that and maintain those
efforts under that issue.
> Improve SQLAnalyzer by parsing result caching
> ---------------------------------------------
>
> Key: TAJO-1430
> URL: https://issues.apache.org/jira/browse/TAJO-1430
> Project: Tajo
> Issue Type: New Feature
> Components: parser
> Affects Versions: 0.10.0
> Reporter: Dongjoon Hyun
> Assignee: Dongjoon Hyun
> Fix For: 0.10.1
>
> Attachments: TAJO-1430.patch, long.sql, middle.sql, wide_table.sql
>
>
> There are wide tables with many many columns. Moveover, BI tools generate
> very complex queries whose size is several MB. Although Tajo executes those
> queries very fast in a few seconds, the total time of UX is slow.
> To become a fastest Hadoop DW, we need this following feature.
> {code:sql}
> time tsql -f middle.sql > /dev/null
> real 0m19.058s
> user 0m2.148s
> sys 0m0.268s
> time tsql -f ~/tajo/middle.sql > /dev/null
> real 0m18.496s
> user 0m2.119s
> sys 0m0.240s
> $ time ./tsql -f ~/tajo/long.sql > /dev/null
> real 0m36.974s
> user 0m2.305s
> sys 0m0.272s
> $ time ./tsql -f ~/tajo/long.sql > /dev/null
> real 0m4.103s
> user 0m2.237s
> sys 0m0.249s
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
