[
https://issues.apache.org/jira/browse/ATLAS-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388949#comment-15388949
]
Sharmadha Sainath commented on ATLAS-1042:
------------------------------------------
Checked with patch applied .
On cluster setup ,
machine 1 - Atlas, Solr
machine 2 - Kafka , Hbase
machine 3 - Hive , client
with,
• atlas.notification.hook.numthreads=5
• kafka topic ATLAS_HOOK created upfront with 5 partitions,
1,000 tables took 1 min 35 secs 834 ms
10,000 tables took 14 mins 34 secs 550 ms
without patch,
1,000 tables took more than 12 mins .
> Performance improvement changes for propertykey+typeName based queries
> ----------------------------------------------------------------------
>
> Key: ATLAS-1042
> URL: https://issues.apache.org/jira/browse/ATLAS-1042
> Project: Atlas
> Issue Type: Bug
> Reporter: Suma Shivaprasad
> Assignee: Suma Shivaprasad
> Attachments: ATLAS-1042.patch
>
>
> The current entity writes which run with qualifiedName + typeName + state
> seem to be running slow since composite indexes do not exist for
> qualifiedName+typeName which seems to explain the regression caused in
> ATLAS-911 which added typeName for unique checks.
> This jira is to address that and possibly explore any other optimizations
> that could be done for propertyKey+typeName based queries like name+typeName
> which are pretty common
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
